terraform

Commit Graph

Author	SHA1	Message	Date
Martin Atkins	e3401947a6	plugin/discovery: PluginRequirements can specify SHA256 digests As well as constraining plugins by version number, we also want to be able to pin plugins to use specific executables so that we can detect drift in available plugins between commands. This commit allows such requirements to be specified, but doesn't yet specify any such requirements, nor validate them.	9 years ago
James Bardin	044ad5ef59	rename some Constraints methods per code review	9 years ago
James Bardin	7d2d951f27	Rename VersionSet to Constraints VersionSet is a wrapper around version.Contraints, so rename it it as such.	9 years ago
Martin Atkins	c20f25a10e	moduledeps: Module.Equals Compares two modules for deep equality. This is primarily provided to enable easy testing of code that constructs module tree structures.	9 years ago
Martin Atkins	e89b5390ca	moduledeps: new package for representing module dependencies As we add support for versioned providers, it's getting more complex to track the dependencies of each module and of the configuration as a whole, so this new package is intended to give us some room to model that nicely as a building block for the various aspects of dependency management. This package is not responsible for building the dependency data structure, since that requires knowledge of core Terraform and that would create cyclic package dependencies. A later change will add some logic in Terraform to create a Module tree based on the combination of a given configuration and state, returning an instance of this package's Module type. The Module.PluginRequirements method flattens the provider-oriented requirements into a set of plugin-oriented requirements (flattening any provider aliases) giving us what we need to work with the plugin/discovery package to find matching installed plugins. Other later uses of this package will include selecting plugin archives to auto-install from releases.hashicorp.com as part of "terraform init", where the module-oriented level of abstraction here should be useful for giving users good, specific feedback when constraints cannot be met. A "reason" is tracked for each provider dependency with the intent that this would later drive a UI for users to see and understand why a given dependency is present, to aid in debugging sticky issues with dependency resolution.	9 years ago

5 Commits (3d3c748ffe409ff548330f7311ced98f9da282d7)