opentofu/terraform/node_provider.go

package terraform

// NodeApplyableProvider represents a provider during an apply.
type NodeApplyableProvider struct {
	*NodeAbstractProvider
}

// GraphNodeEvalable
func (n *NodeApplyableProvider) EvalTree() EvalNode {
	return ProviderEvalTree(n, n.ProviderConfig())
}
terraform: new provider graph node for flattened world 2016-09-15 01:58:16 -05:00			`package terraform`

			`// NodeApplyableProvider represents a provider during an apply.`
			`type NodeApplyableProvider struct {`
terraform: refactor NodeApplyableProvider to use NodeAbstractProvider This is important so that the graph looks correct. 2016-12-03 17:27:38 -06:00			`*NodeAbstractProvider`
terraform: new provider graph node for flattened world 2016-09-15 01:58:16 -05:00			`}`

			`// GraphNodeEvalable`
			`func (n *NodeApplyableProvider) EvalTree() EvalNode {`
WIP reference providers by full name This turned out to be a big messy commit, since the way providers are referenced is tightly coupled throughout the code. That starts to unify how providers are referenced, using the format output node Name method. Add a new field to the internal resource data types called ResolvedProvider. This is set by a new setter method SetProvider when a resource is connected to a provider during graph creation. This allows us to later lookup the provider instance a resource is connected to, without requiring it to have the same module path. The InitProvider context method now takes 2 arguments, one if the provider type and the second is the full name of the provider. While the provider type could still be parsed from the full name, this makes it more explicit and, and changes to the name format won't effect this code. 2017-11-01 17:34:18 -05:00			`return ProviderEvalTree(n, n.ProviderConfig())`
terraform: new provider graph node for flattened world 2016-09-15 01:58:16 -05:00			`}`