boundary

Commit Graph

Author	SHA1	Message	Date
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
Timothy Messier	9d2758368c	doc(schema-diff): Add documentation on schema-diff script This also will include a link to this documentation when leaving a comment on a pull request.	3 years ago
Timothy Messier	04a6c310ee	fix(schema-diff): Include foreign key constraints in diff With the change to report changes to constraints instead of all of the post-data section, foreign key constraints where no longer captured in the diff. This now extracts the foreign key constraints and generates a diff of them between versions. Blame: `b6d58d0c42`	3 years ago
Timothy Messier	b6d58d0c42	ci(schema-diff): Generate one file per constraint (#3082 ) This yeilds a better diff when constraints are changed.	3 years ago
Timothy Messier	b00d888387	ci(schema-diff): Add script to generate diff of database schema (#2924 ) The script should be given a base branch to compare against, if not set it defaults to main. The script will apply the schema migrations for both the base branch and the current commit and generate dumps that are then compared to create a diff. The dumps are left in a temporary directory so that they can be compared using a users preferred diff tool. For example, generate the dumps and diff against main ./scripts/schema-diff.sh main Examine the diff to database functions using delta: delta .schema-diff/funcs_$(git rev-parse main) .schema-diff/funcs_$(git rev-parse HEAD) This also adds a github action that runs the script on pull-requests that contain schema changes and reports the diffs as a comment on the pull-request. Co-authored-by: Hugo Vieira <hugoamvieira@users.noreply.github.com>	3 years ago

5 Commits (v0.21.1)