terraform

Commit Graph

Author	SHA1	Message	Date
Martin Atkins	23caaf9feb	v0.11.0-beta1	9 years ago
Martin Atkins	37e276e043	core: test correct behavior of plan+apply with unstable values We have a few pesky functions that don't act like proper functions and instead return different values on each call. These are tricky because we need to make sure we don't trip over ourselves by re-generating these between plan and apply. Here we add a context test to verify correct behavior in the presence of such functions. There's actually a pre-existing bug which this test caught as originally written: we re-evaluate the interpolation expressions during apply, causing these unstable functions to produce new values, and so the applied value ends up not exactly matching the plan. This is a bug that needs fixing, but it's been around at least since v0.7.6 (random old version I tried this with to see) so we'll put it on the list and address it separately. For now, this part of the test is commented out with a TODO attached.	9 years ago
Martin Atkins	c003e8f9a6	core: don't compare attribute values in Diff.Same We previously didn't compare values but had a TODO to start doing so, which we then recently did. Unfortunately it turns out that we _depend_ on not comparing values here, because when we use EvalCompareDiff (a key user of Diff.Same) we pass in a diff made from a fresh re-interpolation of the configuration and so any non-pure function results (timestamp, uuid) have produced different values.	9 years ago
Martin Atkins	46d2b76e5f	Update CHANGELOG.md	9 years ago
Martin Atkins	46a8deb8d1	Update CHANGELOG.md	9 years ago
Martin Atkins	3b180d7f8a	Merge #16543 : Bring the "terraform" provider back into core	9 years ago
Martin Atkins	d4ee58ce59	Re-integrate the "terraform" provider into the main binary As part of the 0.10 core/provider split we moved this provider, along with all the others, out into its own repository. In retrospect, the "terraform" provider doesn't really make sense to be separated since it's just a thin wrapper around some core code anyway, and so re-integrating it into core avoids the confusion that results when Terraform Core and the terraform provider have inconsistent versions of the backend code and dependencies. There is no good reason to use a different version of the backend code in the provider than in core, so this new "internal provider" mechanism is stricter than the old one: it's not possible to use an external build of this provider at all, and version constraints for it are rejected as a result. This provider is also run in-process rather than in a child process, since again it's just a very thin wrapper around code that's already running in Terraform core anyway, and so the process barrier between the two does not create enough advantage to warrant the additional complexity.	9 years ago
James Bardin	f25d08061d	Merge pull request #16542 from hashicorp/jbardin/module-ui update init output	9 years ago
Masayuki Morita	3efb163edd	Update CHANGELOG.md	9 years ago
James Bardin	964054efc0	update tests for updated output	9 years ago
James Bardin	f3470de2f0	Merge pull request #16546 from hashicorp/jbardin/mmissing-provider-transformer further simplify the missing provider transformer	9 years ago
James Bardin	2ed529f81a	update from review Reference modules by terraform address Unquote versions	9 years ago
James Bardin	c510473fd2	remove code added by stale vim buffer	9 years ago
James Bardin	1bf64ec788	add "Updating" output and fix output tests	9 years ago
James Bardin	9c334fe012	update init output Change "Downloading" to 'Initializing" to match the provider loading dialog. List each module being loaded. If a regisry module is being downloaded, list the registry host, and the version discovered. Show the source string from the config that is being fetched, rather than the go-getter url. The full source can be found in the logs for debugging. Add much more extensive logging	9 years ago
Paul Stack	002200b8f1	websites/workspaces: Add Manta to the list of workspace backends (#16545 ) As Manta backend has now been merged, this should have been done in the same PR - apologises for that	9 years ago
James Bardin	9b489c452e	further simplify the missing provider transformer We can remove the AllowAny option which is no longer used, and providers don't need to be connected to their resources at this stage, since that will happen in the ProviderTransformer.	9 years ago
Tom Harvey	84d18ad579	Updating to include #16296	9 years ago
Tom Harvey	25c3a879db	Adding `azurerm` to the list of supported backends (#16531 ) Fixes #16530	9 years ago
James Bardin	89b931e18a	Merge pull request #16540 from hashicorp/jbardin/provider-inheritance New provider inheritance	9 years ago
James Bardin	ecdba2b0b2	add transform step logs from GraphTransformMulti	9 years ago
James Bardin	b4e9240679	remove implicit provier tests from config/module No longer needed	9 years ago
James Bardin	523b121341	fix get test working directory use a temp dir and cleanup	9 years ago
James Bardin	241dae7ead	resintate disabled tests Reinstate the disabled tests that required some sort of inheritance during graph evaluation.	9 years ago
James Bardin	05ef30be2c	udpate test graph outputs Some of the test graph outputs have changes now that implicit providers are no longer added in the config.	9 years ago
James Bardin	838ffafc18	stop adding implicit provider configs Now that providers in the graph can adopt resources without an explicit provider, there's no need to add the implicit configs to the module.Tree when loading.	9 years ago
James Bardin	a782568645	simplify MissingProvider and ParentProvider transf Simplify the MissingProviderTransformer so that it only adds missing providers at the root level. There's no need for the multitple providers added at every level of the path ParentProviderTransformer then only needs to connect providers with the equivalent type at the root level.	9 years ago
James Bardin	341ec39174	udpate more tests to remove intermediate providers The new missing provider transformer doesn't add these nay longer	9 years ago
James Bardin	94ee4d9111	Add new test and update graph outputs The the grandChild missing test has a provider declared in a child module which is missing in a grandchildmodule. Verify that the grandchild gets connected to the child provider, and they all are connected to the root providers. Update some test outputs to match the expected behavior of only adding missing providers at the root level.	9 years ago
James Bardin	2f91007999	group the provider transformations The series of provider transformations is important, and often repeated. Group these together in a single transform function.	9 years ago
James Bardin	12a4a29cbd	update missing provider transform test The CloserProviderTransformer requires that the resources be connected to their provider first, so that it cen get the correct dependencies, and adding the ProviderTransformer changed the test output slightly.	9 years ago
James Bardin	8388dfd2f9	update GraphBuilder_targetModule test The updates CLoseProviderTransformer connects all provider instances, which is technically the correct behavior.	9 years ago
James Bardin	a14fd0344c	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.	9 years ago
James Bardin	1d54d4b10d	WIP start only referring to provier by adddress Don't try to build a full adress based on the context path for providers in EvalContextBuiltin. Only use the name explicitly provided.	9 years ago
James Bardin	f0727501c1	WIP only add missing providers at the root level When looking for providers to connect to resources, walk up the resource path to find the appropriate provider.	9 years ago
James Bardin	0986d01223	add providers directly from the configuration The first step in only using the required provider nodes in a graph is to be able to specifically add them from the configuration. The MissingProviderTransformer was previously responsible for adding all providers. Now it is really just adding any that are missing from the config.	9 years ago
Martin Atkins	bcc5dffea2	provider/terraform: import terraform provider back into core	9 years ago
Martin Atkins	a3ced1a367	provider/terraform: reorganize for merge into core The "terraform" provider was previously split out into its own repository, but that turned out to be a mistake due to how tightly it depends on aspects of Terraform Core. Here we prepare to bring it back into the core repository by reorganizing the directory layout to conform with what's expected there.	9 years ago
Martin Atkins	da61627b9c	Update CHANGELOG.md	9 years ago
Martin Atkins	6d6a80fd9d	Update CHANGELOG.md	9 years ago
Martin Atkins	9d77d35f53	Update CHANGELOG.md	9 years ago
Martin Atkins	3da5fefdc1	command: Allow TF_DATA_DIR env var to override data directory This allows the user to customize the location where Terraform stores the files normally placed in the ".terraform" subdirectory, if e.g. the current working directory is not writable.	9 years ago
Martin Atkins	4787428cad	Merge #14887 : Custom diff logic for providers	9 years ago
Chris Marchesi	0c0ae3ca7c	helper/schema: CustomizeDiff allowed on writable resources only This keeps CustomizeDiff from being defined on data sources, where it would be useless. We just catch this in InternalValidate like the rest of the CRUD functions that are not used in data sources.	9 years ago
Chris Marchesi	2c541e8c97	helper/schema: Add behaviour detail to various custom diff comments Added some more detailed comments to CustomizeDiff's comments. The new comments detail how CustomizeDiff will be called in the event of different scenarios like creating a new resource, diffing an existing one, diffing an existing resource that has a change that requires a new resource, and destroy/tainted resources. Also added similar detail to ForceNew in ResourceDiff. This should help mitigate any confusion that may come up when using CustomizeDiff, especially in the ForceNew scenario when the second run happens with no state.	9 years ago
James Bardin	229c70cabe	Merge pull request #16296 from stack72/manta-backend Migrate Manta Remote state to be a backend	9 years ago
Radek Simko	b599dc6471	Make CoC and support channels more visible https://help.github.com/articles/adding-a-code-of-conduct-to-your-project/ https://help.github.com/articles/adding-support-resources-to-your-project/	9 years ago
Chris Marchesi	5031767b93	terraform: Add more exception cases for value comparison Needed to add more cases to support value comparison exceptions that the rest of TF expects to work (this fixes tests in various places). Also moved things to a switch block so that it's a little more compact.	9 years ago
Chris Marchesi	12378b4ee2	terraform: Add value check to diff.Same A diff new needs to pass basic value checks to be considered the "same". Several provisions have been added to ensure that the list, set, and RequiresNew behaviours that have needed some exceptions in the past are preserved in this new logic. This ensures that we are checking for value equality as much as possible, which will be more important when we transition to the possibility of diffs being sourced from external data.	9 years ago
Chris Marchesi	f5bdbc0911	helper/schema: Simplify setDiff, remove exported SetDiff mentions setDiff does not make use of its new parameter anymore, so it has been removed. Also, as there is no more SetDiff (exported) function, mentions of that have been removed from comments too.	9 years ago

1 2 3 4 5 ...

20828 Commits (23caaf9feb50d566329f5b4aa07a57da8cd6f448) All Branches Search

20828 Commits (23caaf9feb50d566329f5b4aa07a57da8cd6f448)

All Branches