DecodeFileBody takes a body that is assumed to represent the root of a .tfstack.hcl or .tfstack.json file and decodes the declarations inside.

LoadConfigDir loads, parses, decodes, and partially-validates the stack configuration rooted at the given source address.

LoadSingleStackConfig loads the configuration for only a single stack from the given source address.

NewEmptyConfig returns a representation of an empty configuration that's primarily intended for unit testing situations that don't actually depend on any configuration objects being present.

ParseFileSource parses the given source code as the content of either a .tfstack.hcl or .tfstack.json file, and then delegates the result to [DecodeFileBody] for analysis, returning that final result.

Component represents the declaration of a single component within a particular [Stack].

Config represents an overall stack configuration tree, consisting of a root stack that might optionally have embedded stacks inside it, and so on for arbitrary levels of nesting.

ConfigNode represents a node in a tree of stacks that are to be planned and applied together.

Declarations represent the various items that can be declared in a stack configuration.

EmbeddedStack describes a call to another stack configuration whose declarations should be included as part of the overall stack configuration tree.

File represents the content of a single .tfstack.hcl or .tfstack.json file before it's been merged with its siblings in the same directory to produce the overall [Stack] object.

InputVariable is a declaration of an input variable within a stack configuration.

LocalValue is a declaration of a private local value within a particular stack configuration.

OutputValue is a declaration of a result from a stack configuration, which can be read by the stack's caller.

ProviderConfig is a provider configuration declared within a [Stack].

Removed represents a component that was removed from the configuration.

Stack represents a single stack, which can potentially call other "embedded stacks" in a similar manner to how Terraform modules can call other modules.

TypeConstraint represents all of the type constraint information for either an input variable or an output value.