6 Commits (add-missing-variable-loading)

Author	SHA1	Message	Date
Radek Simko	0fe906fa8c	make copyrightfix	3 months ago
Liam Cervante	915b174da3	stacks: split the terraform1 RPC package into per-service packages (#35513) ... * stacks: split the terraform1 RPC package into per-service packages * pull latest changes	2 years ago
Michael Yocca	ee5cda7000	feat(stacks): add CLI config in RPC API handshake (#35146) ... Adds support for including fields typically found in the Terraform CLI configuration in the RPC API handshake. This allows us to include global configuration arguments that impact the RPC API session without requiring instrumentation for each RPC service. The new Config struct currently supports only service discovery credentials, but it can be expanded in the future.	2 years ago
Martin Atkins	67d8a5137b	rpcapi+stacks: Stacks runtime can see whether experiments are allowed ... We allow experiments only in alpha builds, and so we propagate the flag for whether that's allowed in from "package main". We previously had that plumbed in only as far as the rpcapi startup. This plumbs the flag all the way into package stackeval so that we can in turn propagate it to Terraform's module config loader, which is ultimately the one responsible for ensuring that language experiments can be enabled only when the flag is set. Therefore it will now be possible to opt in to language experiments in modules that are used in stack components.	2 years ago
Martin Atkins	ac93c1bb82	rpcapi: Add HashiCorp copyright comments	3 years ago
Martin Atkins	10d665181a	rpcapi: NewInternalClient returns a socketless RPC client ... Right now we are only using rpcapi from external callers inside Terraform Cloud, but in the long run we will also want to expose equivalent functionality through Terraform CLI. rpcapi.NewInternalClient provides a relatively-lightweight way to achieve that without requiring a child process and sockets. Instead, it just allocates a buffer and passes gRPC messages between client and server using that buffer. This is of course still not as efficient as a direct function call, but the kinds of operations that RPC API exposes tend to have far more expensive elements than the RPC call itself, and using the RPC protocol as the internal API should begin to establish a more explicit architecture boundary between Terraform CLI and Terraform Core, so that clients of the RPC API have the same level of access to Terraform Core as the CLI workflow does. So far we don't have any internal callers for this because nothing in the RPC API has a corresponding CLI entry point. The first callers of this internal RPC interface will probably be the commands providing the CLI-driven development workflow for stacks.	3 years ago