2018-02-28 19:09:48 -06:00
|
|
|
package command
|
|
|
|
|
|
|
|
import (
|
2019-03-07 14:07:13 -06:00
|
|
|
"context"
|
2018-02-28 19:09:48 -06:00
|
|
|
"fmt"
|
|
|
|
"os"
|
|
|
|
"path/filepath"
|
2018-03-27 17:31:05 -05:00
|
|
|
"sort"
|
2018-02-28 19:09:48 -06:00
|
|
|
|
2019-09-09 17:58:44 -05:00
|
|
|
"github.com/hashicorp/hcl/v2"
|
|
|
|
"github.com/hashicorp/hcl/v2/hclsyntax"
|
command: "terraform init" can partially initialize for 0.12upgrade
There are a few constructs from 0.11 and prior that cause 0.12 parsing to
fail altogether, which previously created a chicken/egg problem because
we need to install the providers in order to run "terraform 0.12upgrade"
and thus fix the problem.
This changes "terraform init" to use the new "early configuration" loader
for module and provider installation. This is built on the more permissive
parser in the terraform-config-inspect package, and so it allows us to
read out the top-level blocks from the configuration while accepting
legacy HCL syntax.
In the long run this will let us do version compatibility detection before
attempting a "real" config load, giving us better error messages for any
future syntax additions, but in the short term the key thing is that it
allows us to install the dependencies even if the configuration isn't
fully valid.
Because backend init still requires full configuration, this introduces a
new mode of terraform init where it detects heuristically if it seems like
we need to do a configuration upgrade and does a partial init if so,
before finally directing the user to run "terraform 0.12upgrade" before
running any other commands.
The heuristic here is based on two assumptions:
- If the "early" loader finds no errors but the normal loader does, the
configuration is likely to be valid for Terraform 0.11 but not 0.12.
- If there's already a version constraint in the configuration that
excludes Terraform versions prior to v0.12 then the configuration is
probably _already_ upgraded and so it's just a normal syntax error,
even if the early loader didn't detect it.
Once the upgrade process is removed in 0.13.0 (users will be required to
go stepwise 0.11 -> 0.12 -> 0.13 to upgrade after that), some of this can
be simplified to remove that special mode, but the idea of doing the
dependency version checks against the liberal parser will remain valuable
to increase our chances of reporting version-based incompatibilities
rather than syntax errors as we add new features in future.
2019-01-14 13:11:00 -06:00
|
|
|
"github.com/hashicorp/terraform-config-inspect/tfconfig"
|
2021-05-17 14:17:09 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/configs"
|
|
|
|
"github.com/hashicorp/terraform/internal/configs/configload"
|
|
|
|
"github.com/hashicorp/terraform/internal/configs/configschema"
|
2019-03-07 14:07:13 -06:00
|
|
|
"github.com/hashicorp/terraform/internal/earlyconfig"
|
2019-01-08 20:39:14 -06:00
|
|
|
"github.com/hashicorp/terraform/internal/initwd"
|
2021-05-17 11:45:36 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/registry"
|
2021-05-17 14:46:19 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/terraform"
|
2021-05-17 12:11:06 -05:00
|
|
|
"github.com/hashicorp/terraform/internal/tfdiags"
|
2018-02-28 19:09:48 -06:00
|
|
|
"github.com/zclconf/go-cty/cty"
|
2018-03-27 17:31:05 -05:00
|
|
|
"github.com/zclconf/go-cty/cty/convert"
|
2018-02-28 19:09:48 -06:00
|
|
|
)
|
|
|
|
|
|
|
|
// normalizePath normalizes a given path so that it is, if possible, relative
|
|
|
|
// to the current working directory. This is primarily used to prepare
|
|
|
|
// paths used to load configuration, because we want to prefer recording
|
|
|
|
// relative paths in source code references within the configuration.
|
|
|
|
func (m *Meta) normalizePath(path string) string {
|
2021-09-01 19:01:44 -05:00
|
|
|
m.fixupMissingWorkingDir()
|
|
|
|
return m.WorkingDir.NormalizePath(path)
|
2018-02-28 19:09:48 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
// loadConfig reads a configuration from the given directory, which should
|
|
|
|
// contain a root module and have already have any required descendent modules
|
|
|
|
// installed.
|
|
|
|
func (m *Meta) loadConfig(rootDir string) (*configs.Config, tfdiags.Diagnostics) {
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
rootDir = m.normalizePath(rootDir)
|
|
|
|
|
|
|
|
loader, err := m.initConfigLoader()
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(err)
|
|
|
|
return nil, diags
|
|
|
|
}
|
|
|
|
|
|
|
|
config, hclDiags := loader.LoadConfig(rootDir)
|
|
|
|
diags = diags.Append(hclDiags)
|
|
|
|
return config, diags
|
|
|
|
}
|
|
|
|
|
|
|
|
// loadSingleModule reads configuration from the given directory and returns
|
|
|
|
// a description of that module only, without attempting to assemble a module
|
|
|
|
// tree for referenced child modules.
|
|
|
|
//
|
|
|
|
// Most callers should use loadConfig. This method exists to support early
|
|
|
|
// initialization use-cases where the root module must be inspected in order
|
|
|
|
// to determine what else needs to be installed before the full configuration
|
|
|
|
// can be used.
|
|
|
|
func (m *Meta) loadSingleModule(dir string) (*configs.Module, tfdiags.Diagnostics) {
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
dir = m.normalizePath(dir)
|
|
|
|
|
|
|
|
loader, err := m.initConfigLoader()
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(err)
|
|
|
|
return nil, diags
|
|
|
|
}
|
|
|
|
|
|
|
|
module, hclDiags := loader.Parser().LoadConfigDir(dir)
|
|
|
|
diags = diags.Append(hclDiags)
|
|
|
|
return module, diags
|
|
|
|
}
|
|
|
|
|
command: "terraform init" can partially initialize for 0.12upgrade
There are a few constructs from 0.11 and prior that cause 0.12 parsing to
fail altogether, which previously created a chicken/egg problem because
we need to install the providers in order to run "terraform 0.12upgrade"
and thus fix the problem.
This changes "terraform init" to use the new "early configuration" loader
for module and provider installation. This is built on the more permissive
parser in the terraform-config-inspect package, and so it allows us to
read out the top-level blocks from the configuration while accepting
legacy HCL syntax.
In the long run this will let us do version compatibility detection before
attempting a "real" config load, giving us better error messages for any
future syntax additions, but in the short term the key thing is that it
allows us to install the dependencies even if the configuration isn't
fully valid.
Because backend init still requires full configuration, this introduces a
new mode of terraform init where it detects heuristically if it seems like
we need to do a configuration upgrade and does a partial init if so,
before finally directing the user to run "terraform 0.12upgrade" before
running any other commands.
The heuristic here is based on two assumptions:
- If the "early" loader finds no errors but the normal loader does, the
configuration is likely to be valid for Terraform 0.11 but not 0.12.
- If there's already a version constraint in the configuration that
excludes Terraform versions prior to v0.12 then the configuration is
probably _already_ upgraded and so it's just a normal syntax error,
even if the early loader didn't detect it.
Once the upgrade process is removed in 0.13.0 (users will be required to
go stepwise 0.11 -> 0.12 -> 0.13 to upgrade after that), some of this can
be simplified to remove that special mode, but the idea of doing the
dependency version checks against the liberal parser will remain valuable
to increase our chances of reporting version-based incompatibilities
rather than syntax errors as we add new features in future.
2019-01-14 13:11:00 -06:00
|
|
|
// loadSingleModuleEarly is a variant of loadSingleModule that uses the special
|
|
|
|
// "early config" loader that is more forgiving of unexpected constructs and
|
|
|
|
// legacy syntax.
|
|
|
|
//
|
|
|
|
// Early-loaded config is not registered in the source code cache, so
|
|
|
|
// diagnostics produced from it may render without source code snippets. In
|
|
|
|
// practice this is not a big concern because the early config loader also
|
|
|
|
// cannot generate detailed source locations, so it prefers to produce
|
|
|
|
// diagnostics without explicit source location information and instead includes
|
|
|
|
// approximate locations in the message text.
|
|
|
|
//
|
|
|
|
// Most callers should use loadConfig. This method exists to support early
|
|
|
|
// initialization use-cases where the root module must be inspected in order
|
|
|
|
// to determine what else needs to be installed before the full configuration
|
|
|
|
// can be used.
|
|
|
|
func (m *Meta) loadSingleModuleEarly(dir string) (*tfconfig.Module, tfdiags.Diagnostics) {
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
dir = m.normalizePath(dir)
|
|
|
|
|
|
|
|
module, moreDiags := earlyconfig.LoadModule(dir)
|
|
|
|
diags = diags.Append(moreDiags)
|
|
|
|
|
|
|
|
return module, diags
|
|
|
|
}
|
|
|
|
|
2018-03-27 17:31:05 -05:00
|
|
|
// dirIsConfigPath checks if the given path is a directory that contains at
|
|
|
|
// least one Terraform configuration file (.tf or .tf.json), returning true
|
|
|
|
// if so.
|
|
|
|
//
|
|
|
|
// In the unlikely event that the underlying config loader cannot be initalized,
|
|
|
|
// this function optimistically returns true, assuming that the caller will
|
|
|
|
// then do some other operation that requires the config loader and get an
|
|
|
|
// error at that point.
|
|
|
|
func (m *Meta) dirIsConfigPath(dir string) bool {
|
|
|
|
loader, err := m.initConfigLoader()
|
|
|
|
if err != nil {
|
|
|
|
return true
|
|
|
|
}
|
|
|
|
|
|
|
|
return loader.IsConfigDir(dir)
|
|
|
|
}
|
|
|
|
|
2018-03-20 20:43:02 -05:00
|
|
|
// loadBackendConfig reads configuration from the given directory and returns
|
|
|
|
// the backend configuration defined by that module, if any. Nil is returned
|
|
|
|
// if the specified module does not have an explicit backend configuration.
|
|
|
|
//
|
|
|
|
// This is a convenience method for command code that will delegate to the
|
|
|
|
// configured backend to do most of its work, since in that case it is the
|
|
|
|
// backend that will do the full configuration load.
|
|
|
|
//
|
|
|
|
// Although this method returns only the backend configuration, at present it
|
|
|
|
// actually loads and validates the entire configuration first. Therefore errors
|
|
|
|
// returned may be about other aspects of the configuration. This behavior may
|
|
|
|
// change in future, so callers must not rely on it. (That is, they must expect
|
|
|
|
// that a call to loadSingleModule or loadConfig could fail on the same
|
|
|
|
// directory even if loadBackendConfig succeeded.)
|
|
|
|
func (m *Meta) loadBackendConfig(rootDir string) (*configs.Backend, tfdiags.Diagnostics) {
|
|
|
|
mod, diags := m.loadSingleModule(rootDir)
|
2019-12-06 08:46:03 -06:00
|
|
|
|
|
|
|
// Only return error diagnostics at this point. Any warnings will be caught
|
|
|
|
// again later and duplicated in the output.
|
2019-03-12 16:57:26 -05:00
|
|
|
if diags.HasErrors() {
|
|
|
|
return nil, diags
|
|
|
|
}
|
2021-08-24 14:28:12 -05:00
|
|
|
|
|
|
|
if mod.CloudConfig != nil {
|
|
|
|
backendConfig := mod.CloudConfig.ToBackendConfig()
|
|
|
|
return &backendConfig, nil
|
|
|
|
}
|
|
|
|
|
2019-12-06 08:46:03 -06:00
|
|
|
return mod.Backend, nil
|
2018-03-20 20:43:02 -05:00
|
|
|
}
|
|
|
|
|
2018-03-27 17:31:05 -05:00
|
|
|
// loadHCLFile reads an arbitrary HCL file and returns the unprocessed body
|
|
|
|
// representing its toplevel. Most callers should use one of the more
|
|
|
|
// specialized "load..." methods to get a higher-level representation.
|
|
|
|
func (m *Meta) loadHCLFile(filename string) (hcl.Body, tfdiags.Diagnostics) {
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
filename = m.normalizePath(filename)
|
|
|
|
|
|
|
|
loader, err := m.initConfigLoader()
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(err)
|
|
|
|
return nil, diags
|
|
|
|
}
|
|
|
|
|
|
|
|
body, hclDiags := loader.Parser().LoadHCLFile(filename)
|
|
|
|
diags = diags.Append(hclDiags)
|
|
|
|
return body, diags
|
|
|
|
}
|
|
|
|
|
2018-02-28 19:09:48 -06:00
|
|
|
// installModules reads a root module from the given directory and attempts
|
|
|
|
// recursively install all of its descendent modules.
|
|
|
|
//
|
|
|
|
// The given hooks object will be notified of installation progress, which
|
|
|
|
// can then be relayed to the end-user. The moduleUiInstallHooks type in
|
|
|
|
// this package has a reasonable implementation for displaying notifications
|
|
|
|
// via a provided cli.Ui.
|
2019-01-08 20:39:14 -06:00
|
|
|
func (m *Meta) installModules(rootDir string, upgrade bool, hooks initwd.ModuleInstallHooks) tfdiags.Diagnostics {
|
2018-02-28 19:09:48 -06:00
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
rootDir = m.normalizePath(rootDir)
|
|
|
|
|
|
|
|
err := os.MkdirAll(m.modulesDir(), os.ModePerm)
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(fmt.Errorf("failed to create local modules directory: %s", err))
|
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
2019-01-08 20:39:14 -06:00
|
|
|
inst := m.moduleInstaller()
|
command: "terraform init" can partially initialize for 0.12upgrade
There are a few constructs from 0.11 and prior that cause 0.12 parsing to
fail altogether, which previously created a chicken/egg problem because
we need to install the providers in order to run "terraform 0.12upgrade"
and thus fix the problem.
This changes "terraform init" to use the new "early configuration" loader
for module and provider installation. This is built on the more permissive
parser in the terraform-config-inspect package, and so it allows us to
read out the top-level blocks from the configuration while accepting
legacy HCL syntax.
In the long run this will let us do version compatibility detection before
attempting a "real" config load, giving us better error messages for any
future syntax additions, but in the short term the key thing is that it
allows us to install the dependencies even if the configuration isn't
fully valid.
Because backend init still requires full configuration, this introduces a
new mode of terraform init where it detects heuristically if it seems like
we need to do a configuration upgrade and does a partial init if so,
before finally directing the user to run "terraform 0.12upgrade" before
running any other commands.
The heuristic here is based on two assumptions:
- If the "early" loader finds no errors but the normal loader does, the
configuration is likely to be valid for Terraform 0.11 but not 0.12.
- If there's already a version constraint in the configuration that
excludes Terraform versions prior to v0.12 then the configuration is
probably _already_ upgraded and so it's just a normal syntax error,
even if the early loader didn't detect it.
Once the upgrade process is removed in 0.13.0 (users will be required to
go stepwise 0.11 -> 0.12 -> 0.13 to upgrade after that), some of this can
be simplified to remove that special mode, but the idea of doing the
dependency version checks against the liberal parser will remain valuable
to increase our chances of reporting version-based incompatibilities
rather than syntax errors as we add new features in future.
2019-01-14 13:11:00 -06:00
|
|
|
_, moreDiags := inst.InstallModules(rootDir, upgrade, hooks)
|
2019-01-08 20:39:14 -06:00
|
|
|
diags = diags.Append(moreDiags)
|
2018-02-28 19:09:48 -06:00
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
|
|
|
// initDirFromModule initializes the given directory (which should be
|
|
|
|
// pre-verified as empty by the caller) by copying the source code from the
|
|
|
|
// given module address.
|
|
|
|
//
|
|
|
|
// Internally this runs similar steps to installModules.
|
|
|
|
// The given hooks object will be notified of installation progress, which
|
|
|
|
// can then be relayed to the end-user. The moduleUiInstallHooks type in
|
|
|
|
// this package has a reasonable implementation for displaying notifications
|
|
|
|
// via a provided cli.Ui.
|
2019-01-08 20:39:14 -06:00
|
|
|
func (m *Meta) initDirFromModule(targetDir string, addr string, hooks initwd.ModuleInstallHooks) tfdiags.Diagnostics {
|
2018-02-28 19:09:48 -06:00
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
targetDir = m.normalizePath(targetDir)
|
2019-01-08 20:39:14 -06:00
|
|
|
moreDiags := initwd.DirFromModule(targetDir, m.modulesDir(), addr, m.registryClient(), hooks)
|
|
|
|
diags = diags.Append(moreDiags)
|
2018-02-28 19:09:48 -06:00
|
|
|
return diags
|
|
|
|
}
|
|
|
|
|
2018-03-27 17:31:05 -05:00
|
|
|
// inputForSchema uses interactive prompts to try to populate any
|
|
|
|
// not-yet-populated required attributes in the given object value to
|
|
|
|
// comply with the given schema.
|
|
|
|
//
|
|
|
|
// An error will be returned if input is disabled for this meta or if
|
|
|
|
// values cannot be obtained for some other operational reason. Errors are
|
|
|
|
// not returned for invalid input since the input loop itself will report
|
|
|
|
// that interactively.
|
|
|
|
//
|
|
|
|
// It is not guaranteed that the result will be valid, since certain attribute
|
|
|
|
// types and nested blocks are not supported for input.
|
|
|
|
//
|
|
|
|
// The given value must conform to the given schema. If not, this method will
|
|
|
|
// panic.
|
|
|
|
func (m *Meta) inputForSchema(given cty.Value, schema *configschema.Block) (cty.Value, error) {
|
|
|
|
if given.IsNull() || !given.IsKnown() {
|
|
|
|
// This is not reasonable input, but we'll tolerate it anyway and
|
|
|
|
// just pass it through for the caller to handle downstream.
|
|
|
|
return given, nil
|
|
|
|
}
|
|
|
|
|
2018-11-01 13:59:07 -05:00
|
|
|
retVals := given.AsValueMap()
|
2018-03-27 17:31:05 -05:00
|
|
|
names := make([]string, 0, len(schema.Attributes))
|
|
|
|
for name, attrS := range schema.Attributes {
|
2018-11-01 13:59:07 -05:00
|
|
|
if attrS.Required && retVals[name].IsNull() && attrS.Type.IsPrimitiveType() {
|
2018-03-27 17:31:05 -05:00
|
|
|
names = append(names, name)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
sort.Strings(names)
|
|
|
|
|
|
|
|
input := m.UIInput()
|
|
|
|
for _, name := range names {
|
|
|
|
attrS := schema.Attributes[name]
|
|
|
|
|
|
|
|
for {
|
2019-03-07 14:07:13 -06:00
|
|
|
strVal, err := input.Input(context.Background(), &terraform.InputOpts{
|
2018-03-27 17:31:05 -05:00
|
|
|
Id: name,
|
|
|
|
Query: name,
|
|
|
|
Description: attrS.Description,
|
|
|
|
})
|
|
|
|
if err != nil {
|
|
|
|
return cty.UnknownVal(schema.ImpliedType()), fmt.Errorf("%s: %s", name, err)
|
|
|
|
}
|
|
|
|
|
|
|
|
val := cty.StringVal(strVal)
|
|
|
|
val, err = convert.Convert(val, attrS.Type)
|
|
|
|
if err != nil {
|
|
|
|
m.showDiagnostics(fmt.Errorf("Invalid value: %s", err))
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
|
|
|
|
retVals[name] = val
|
|
|
|
break
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return cty.ObjectVal(retVals), nil
|
|
|
|
}
|
|
|
|
|
2018-02-28 19:09:48 -06:00
|
|
|
// configSources returns the source cache from the receiver's config loader,
|
|
|
|
// which the caller must not modify.
|
|
|
|
//
|
|
|
|
// If a config loader has not yet been instantiated then no files could have
|
|
|
|
// been loaded already, so this method returns a nil map in that case.
|
|
|
|
func (m *Meta) configSources() map[string][]byte {
|
|
|
|
if m.configLoader == nil {
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
return m.configLoader.Sources()
|
|
|
|
}
|
|
|
|
|
|
|
|
func (m *Meta) modulesDir() string {
|
|
|
|
return filepath.Join(m.DataDir(), "modules")
|
|
|
|
}
|
|
|
|
|
2018-10-09 19:47:53 -05:00
|
|
|
// registerSynthConfigSource allows commands to add synthetic additional source
|
|
|
|
// buffers to the config loader's cache of sources (as returned by
|
|
|
|
// configSources), which is useful when a command is directly parsing something
|
|
|
|
// from the command line that may produce diagnostics, so that diagnostic
|
|
|
|
// snippets can still be produced.
|
|
|
|
//
|
|
|
|
// If this is called before a configLoader has been initialized then it will
|
|
|
|
// try to initialize the loader but ignore any initialization failure, turning
|
|
|
|
// the call into a no-op. (We presume that a caller will later call a different
|
|
|
|
// function that also initializes the config loader as a side effect, at which
|
|
|
|
// point those errors can be returned.)
|
|
|
|
func (m *Meta) registerSynthConfigSource(filename string, src []byte) {
|
|
|
|
loader, err := m.initConfigLoader()
|
|
|
|
if err != nil || loader == nil {
|
|
|
|
return // treated as no-op, since this is best-effort
|
|
|
|
}
|
|
|
|
loader.Parser().ForceFileSource(filename, src)
|
|
|
|
}
|
|
|
|
|
2018-02-28 19:09:48 -06:00
|
|
|
// initConfigLoader initializes the shared configuration loader if it isn't
|
|
|
|
// already initialized.
|
|
|
|
//
|
|
|
|
// If the loader cannot be created for some reason then an error is returned
|
|
|
|
// and no loader is created. Subsequent calls will presumably see the same
|
|
|
|
// error. Loader initialization errors will tend to prevent any further use
|
|
|
|
// of most Terraform features, so callers should report any error and safely
|
|
|
|
// terminate.
|
|
|
|
func (m *Meta) initConfigLoader() (*configload.Loader, error) {
|
|
|
|
if m.configLoader == nil {
|
|
|
|
loader, err := configload.NewLoader(&configload.Config{
|
|
|
|
ModulesDir: m.modulesDir(),
|
|
|
|
Services: m.Services,
|
|
|
|
})
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
m.configLoader = loader
|
cli: Add initial command views abstraction
Terraform supports multiple output formats for several sub-commands.
The default format is user-readable text, but many sub-commands support
a `-json` flag to output a machine-readable format for the result. The
output command also supports a `-raw` flag for a simpler, scripting-
focused machine readable format.
This commit adds a "views" abstraction, intended to help ensure
consistency between the various output formats. This extracts the render
specific code from the command package, and moves it into a views
package. Each command is expected to create an interface for its view,
and one or more implementations of that interface.
By doing so, we separate the concerns of generating the sub-command
result from rendering the result in the specified output format. This
should make it easier to ensure that all output formats will be updated
together when changes occur in the result-generating phase.
There are some other consequences of this restructuring:
- Views now directly access the terminal streams, rather than the
now-redundant cli.Ui instance;
- With the reorganization of commands, parsing CLI arguments is now the
responsibility of a separate "arguments" package.
For now, views are added only for the output sub-command, as an example.
Because this command uses code which is shared with the apply and
refresh commands, those are also partially updated.
2021-01-27 14:51:40 -06:00
|
|
|
if m.View != nil {
|
|
|
|
m.View.SetConfigSources(loader.Sources)
|
|
|
|
}
|
2018-02-28 19:09:48 -06:00
|
|
|
}
|
|
|
|
return m.configLoader, nil
|
|
|
|
}
|
2018-03-27 17:31:05 -05:00
|
|
|
|
2019-01-08 20:39:14 -06:00
|
|
|
// moduleInstaller instantiates and returns a module installer for use by
|
|
|
|
// "terraform init" (directly or indirectly).
|
|
|
|
func (m *Meta) moduleInstaller() *initwd.ModuleInstaller {
|
|
|
|
reg := m.registryClient()
|
|
|
|
return initwd.NewModuleInstaller(m.modulesDir(), reg)
|
|
|
|
}
|
|
|
|
|
|
|
|
// registryClient instantiates and returns a new Terraform Registry client.
|
|
|
|
func (m *Meta) registryClient() *registry.Client {
|
|
|
|
return registry.NewClient(m.Services, nil)
|
|
|
|
}
|
|
|
|
|
2018-03-27 17:31:05 -05:00
|
|
|
// configValueFromCLI parses a configuration value that was provided in a
|
|
|
|
// context in the CLI where only strings can be provided, such as on the
|
|
|
|
// command line or in an environment variable, and returns the resulting
|
|
|
|
// value.
|
|
|
|
func configValueFromCLI(synthFilename, rawValue string, wantType cty.Type) (cty.Value, tfdiags.Diagnostics) {
|
|
|
|
var diags tfdiags.Diagnostics
|
|
|
|
|
|
|
|
switch {
|
|
|
|
case wantType.IsPrimitiveType():
|
|
|
|
// Primitive types are handled as conversions from string.
|
|
|
|
val := cty.StringVal(rawValue)
|
|
|
|
var err error
|
|
|
|
val, err = convert.Convert(val, wantType)
|
|
|
|
if err != nil {
|
|
|
|
diags = diags.Append(tfdiags.Sourceless(
|
|
|
|
tfdiags.Error,
|
|
|
|
"Invalid backend configuration value",
|
|
|
|
fmt.Sprintf("Invalid backend configuration argument %s: %s", synthFilename, err),
|
|
|
|
))
|
|
|
|
val = cty.DynamicVal // just so we return something valid-ish
|
|
|
|
}
|
|
|
|
return val, diags
|
|
|
|
default:
|
|
|
|
// Non-primitives are parsed as HCL expressions
|
|
|
|
src := []byte(rawValue)
|
|
|
|
expr, hclDiags := hclsyntax.ParseExpression(src, synthFilename, hcl.Pos{Line: 1, Column: 1})
|
|
|
|
diags = diags.Append(hclDiags)
|
|
|
|
if hclDiags.HasErrors() {
|
|
|
|
return cty.DynamicVal, diags
|
|
|
|
}
|
|
|
|
val, hclDiags := expr.Value(nil)
|
|
|
|
diags = diags.Append(hclDiags)
|
|
|
|
if hclDiags.HasErrors() {
|
|
|
|
val = cty.DynamicVal
|
|
|
|
}
|
|
|
|
return val, diags
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// rawFlags is a flag.Value implementation that just appends raw flag
|
|
|
|
// names and values to a slice.
|
|
|
|
type rawFlags struct {
|
|
|
|
flagName string
|
|
|
|
items *[]rawFlag
|
|
|
|
}
|
|
|
|
|
|
|
|
func newRawFlags(flagName string) rawFlags {
|
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 12:33:53 -05:00
|
|
|
var items []rawFlag
|
2018-03-27 17:31:05 -05:00
|
|
|
return rawFlags{
|
|
|
|
flagName: flagName,
|
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 12:33:53 -05:00
|
|
|
items: &items,
|
2018-03-27 17:31:05 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-16 09:47:32 -05:00
|
|
|
func (f rawFlags) Empty() bool {
|
|
|
|
if f.items == nil {
|
|
|
|
return true
|
|
|
|
}
|
|
|
|
return len(*f.items) == 0
|
|
|
|
}
|
|
|
|
|
2018-03-27 17:31:05 -05:00
|
|
|
func (f rawFlags) AllItems() []rawFlag {
|
2018-11-21 08:35:27 -06:00
|
|
|
if f.items == nil {
|
|
|
|
return nil
|
|
|
|
}
|
2018-03-27 17:31:05 -05:00
|
|
|
return *f.items
|
|
|
|
}
|
|
|
|
|
|
|
|
func (f rawFlags) Alias(flagName string) rawFlags {
|
|
|
|
return rawFlags{
|
|
|
|
flagName: flagName,
|
|
|
|
items: f.items,
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func (f rawFlags) String() string {
|
|
|
|
return ""
|
|
|
|
}
|
|
|
|
|
|
|
|
func (f rawFlags) Set(str string) error {
|
|
|
|
*f.items = append(*f.items, rawFlag{
|
|
|
|
Name: f.flagName,
|
|
|
|
Value: str,
|
|
|
|
})
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
type rawFlag struct {
|
|
|
|
Name string
|
|
|
|
Value string
|
|
|
|
}
|
|
|
|
|
|
|
|
func (f rawFlag) String() string {
|
|
|
|
return fmt.Sprintf("%s=%q", f.Name, f.Value)
|
|
|
|
}
|