IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

tofu: Remove confusing terminology from Context.Eval docstring

Browse Source 
This comment was written using the term "ephemeral values" in a one-off
way that now conflicts with a different use of that terminology in our
community, so we'll just call them "named values" instead since that
matches how we refer collectively to input variables, local values, and
output values elsewhere in this codebase.

Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
This commit is contained in:
Martin Atkins 2024-12-17 14:57:54 -08:00
parent b7038ef037
commit 6e37f8ac16
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
internal/tofu/context_eval.go
View File

@ -24,8 +24,8 @@ type EvalOpts struct {
// Eval produces a scope in which expressions can be evaluated for
// the given module path.
//
// This method must first evaluate any ephemeral values (input variables, local
// values, and output values) in the configuration. These ephemeral values are
// This method must first evaluate any named values (input variables, local
// values, and output values) in the configuration. These named values are
// not included in the persisted state, so they must be re-computed using other
// values in the state before they can be properly evaluated. The updated
// values are retained in the main state associated with the receiving context.