* 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 dbe0968bffd92745d8663c6940debae098395a6b. * 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 4d865a91a7a4f11605f0dc4609355d7e3c3cfffe. --------- Co-authored-by: hashicorp-copywrite[bot] <110428419+hashicorp-copywrite[bot]@users.noreply.github.com> Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
66 lines
2.8 KiB
HCL
66 lines
2.8 KiB
HCL
# Copyright (c) HashiCorp, Inc.
|
|
# SPDX-License-Identifier: BUSL-1.1
|
|
|
|
// Example variable inputs. Set these to valid values and uncomment them before
|
|
// running scenarios.
|
|
|
|
// The AWS region you want to create the resources in. Make sure you choose a
|
|
// region where you've got an AWS keypair.
|
|
// aws_region = "us-east-1"
|
|
|
|
// The name of the AWS keypair. You can look them up in the AWS console on a per-
|
|
// region basis. E.g. https://us-east-1.console.aws.amazon.com/ec2/v2/home?region=us-east-1#KeyPairs:
|
|
// aws_ssh_keypair_name = "mykeypair"
|
|
|
|
// The path to the private key associated with your keypair.
|
|
// aws_ssh_private_key_path = "/Users/<user>/.ssh/mykeypair.pem
|
|
|
|
// The username to use for boundary. The github username of the user who trigger
|
|
// the workflow will be used automatically in the CI.
|
|
// enos_user = "enos"
|
|
|
|
// The app.terraform.io API token for the QTI organization. There is a shared
|
|
// token for the Boundary team in 1Password, or you can request access to the
|
|
// organization by reaching out to the members of #team-quality.
|
|
// tfc_api_token = "xxxxxxxx.atlasv1.xxx...."
|
|
|
|
// The directory that contains the copy of boundary you want to local execution
|
|
// from. `make install` should install it into the $GOBIN, which is usually
|
|
// similar to what is listed below.
|
|
// local_boundary_dir = "/Users/<user>/.go/bin"
|
|
|
|
// The directory that contains the copy of boundary you want to use for e2e tests
|
|
// local_boundary_src_dir = "/Users/<user>/Developer/boundary"
|
|
|
|
// The directory that contains the copy of boundary-ui you want to use for UI tests
|
|
// local_boundary_ui_src_dir = "/Users/<user>/Developer/boundary-ui"
|
|
|
|
// Path to a license file if required
|
|
// boundary_license_path = "./support/boundary.hclic"
|
|
|
|
// Built binary custom name, if not "boundary"
|
|
// boundary_binary_name = "boundary"
|
|
|
|
// Build edition from CRT
|
|
// boundary_edition = "oss"
|
|
|
|
// The path to the installation bundle for the target machines. The existing
|
|
// scenarios all use linux/amd64 architecture so bundle ought to match that
|
|
// architecture. This is only used for variants which use the `crt` builder
|
|
// variant. If you execute variants with the local builder this does not need
|
|
// to be set. In CI we use this to point to the artifacts generated as part
|
|
// of the build workflow.
|
|
// crt_bundle_path = "./boundary_linux_amd64.zip"
|
|
|
|
// The port the ALB will listen on to proxy controller API requests. This defaults
|
|
// to 9200
|
|
// alb_listener_api_port = 9200
|
|
|
|
// Generally, if there's failure in the test suite for any reason, enos/terraform will throw an error and you
|
|
// would not be able to access the environment variables needed to test locally. Enabling this
|
|
// will ensure that the enos scenario passes.
|
|
// e2e_debug_no_run = true
|
|
|
|
// Timeout for `go test` execution in the e2e tests, 10m default
|
|
// go_test_timeout = "10m"
|