2018-04-04 03:11:28 +02:00
|
|
|
package lang
|
|
|
|
|
|
|
|
import (
|
|
|
|
"sync"
|
|
|
|
|
|
|
|
"github.com/zclconf/go-cty/cty/function"
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 19:33:53 +02:00
|
|
|
|
|
|
|
"github.com/hashicorp/terraform/addrs"
|
2020-10-30 22:19:30 +01:00
|
|
|
"github.com/hashicorp/terraform/experiments"
|
2018-04-04 03:11:28 +02:00
|
|
|
)
|
|
|
|
|
|
|
|
// Scope is the main type in this package, allowing dynamic evaluation of
|
|
|
|
// blocks and expressions based on some contextual information that informs
|
|
|
|
// which variables and functions will be available.
|
|
|
|
type Scope struct {
|
|
|
|
// Data is used to resolve references in expressions.
|
|
|
|
Data Data
|
|
|
|
|
terraform: ugly huge change to weave in new HCL2-oriented types
Due to how deeply the configuration types go into Terraform Core, there
isn't a great way to switch out to HCL2 gradually. As a consequence, this
huge commit gets us from the old state to a _compilable_ new state, but
does not yet attempt to fix any tests and has a number of known missing
parts and bugs. We will continue to iterate on this in forthcoming
commits, heading back towards passing tests and making Terraform
fully-functional again.
The three main goals here are:
- Use the configuration models from the "configs" package instead of the
older models in the "config" package, which is now deprecated and
preserved only to help us write our migration tool.
- Do expression inspection and evaluation using the functionality of the
new "lang" package, instead of the Interpolator type and related
functionality in the main "terraform" package.
- Represent addresses of various objects using types in the addrs package,
rather than hand-constructed strings. This is not critical to support
the above, but was a big help during the implementation of these other
points since it made it much more explicit what kind of address is
expected in each context.
Since our new packages are built to accommodate some future planned
features that are not yet implemented (e.g. the "for_each" argument on
resources, "count"/"for_each" on modules), and since there's still a fair
amount of functionality still using old-style APIs, there is a moderate
amount of shimming here to connect new assumptions with old, hopefully in
a way that makes it easier to find and eliminate these shims later.
I apologize in advance to the person who inevitably just found this huge
commit while spelunking through the commit history.
2018-04-30 19:33:53 +02:00
|
|
|
// SelfAddr is the address that the "self" object should be an alias of,
|
|
|
|
// or nil if the "self" object should not be available at all.
|
|
|
|
SelfAddr addrs.Referenceable
|
|
|
|
|
2018-04-04 03:11:28 +02:00
|
|
|
// BaseDir is the base directory used by any interpolation functions that
|
|
|
|
// accept filesystem paths as arguments.
|
|
|
|
BaseDir string
|
|
|
|
|
|
|
|
// PureOnly can be set to true to request that any non-pure functions
|
|
|
|
// produce unknown value results rather than actually executing. This is
|
|
|
|
// important during a plan phase to avoid generating results that could
|
|
|
|
// then differ during apply.
|
|
|
|
PureOnly bool
|
|
|
|
|
|
|
|
funcs map[string]function.Function
|
|
|
|
funcsLock sync.Mutex
|
2020-10-30 22:19:30 +01:00
|
|
|
|
|
|
|
// activeExperiments is an optional set of experiments that should be
|
|
|
|
// considered as active in the module that this scope will be used for.
|
|
|
|
// Callers can populate it by calling the SetActiveExperiments method.
|
|
|
|
activeExperiments experiments.Set
|
2021-04-23 16:29:50 +02:00
|
|
|
|
|
|
|
// ConsoleMode can be set to true to request any console-only functions are
|
|
|
|
// included in this scope.
|
|
|
|
ConsoleMode bool
|
2020-10-30 22:19:30 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
// SetActiveExperiments allows a caller to declare that a set of experiments
|
|
|
|
// is active for the module that the receiving Scope belongs to, which might
|
|
|
|
// then cause the scope to activate some additional experimental behaviors.
|
|
|
|
func (s *Scope) SetActiveExperiments(active experiments.Set) {
|
|
|
|
s.activeExperiments = active
|
2018-04-04 03:11:28 +02:00
|
|
|
}
|