420 Commits (d0278ecf0f69928ff55173e584dfd113e99bc970)

Author	SHA1	Message	Date
James Bardin	1af7ee87a2	Silence log output when not verbose ... Set the default log package output to iotuil.Discard during tests if the `-v` flag isn't set. If we are verbose, then apply the filter according to the TF_LOG env variable.	10 years ago
James Bardin	2747d964cb	Merge pull request #7877 from hashicorp/jbardin/races ... core: Fix race conditions, mostly around diffs	10 years ago
James Nugent	9034196baf	Merge pull request #7875 from hashicorp/b-outputs-by-module ... core: Fix -module for terraform output command	10 years ago
James Nugent	0e4e94a86f	core: Fix -module for terraform output command ... The behaviour whereby outputs for a particular nested module can be output was broken by the changes for lists and maps. This commit restores the previous behaviour by passing the module path into the outputsAsString function. We also add a new test of this since the code path for indivdual output vs all outputs for a module has diverged.	10 years ago
James Bardin	5802f76eaa	Make all terraform package tests pass under -race ... This isn't a pretty refactor, but fixes the race issues in this package for now. Fix race on RawConfig.Config() fix command package races	10 years ago
James Bardin	0c714592f0	Fix variable handling on subsequent pushes ... The handling of remote variables was completely disabled for push. We still need to fetch variables from atlas for push, because if the variable is only set remotely the Input walk will still prompt the user for a value. We add the missing remote variables to the context to disable input. We now only handle remote variables as atlas.TFVar and explicitly pass around that type rather than an `interface{}`. Shorten the text fixture slightly to make the output a little more readable on failures.	10 years ago
James Bardin	b4b70193d2	whitespace fixes	10 years ago
James Bardin	8038e60a20	Add a function to quote HCL strings ... The strings we have in the variables may contain escaped double-quotes, which have already been parsed and had the `\`s removed. We need to re-escape these, but only if we are in the outer string and not inside an interpolation.	10 years ago
James Bardin	de87267697	Add tf_vars to the variables sent in push ... Add tf_vars to the data structures sent in terraform push. This takes any value of type []interface{} or map[string]interface{} and marshals it as a string representation of the equivalent HCL. This prevents ambiguity in atlas between a string that looks like a json structure, and an actual json structure. For the time being we will need a way to serialize data as HCL, so the command package has an internal encodeHCL function to do so. We can remove this if we get complete package for marshaling HCL.	10 years ago
James Nugent	681d94ae20	core: Allow lists and maps as variable overrides ... Terraform 0.7 introduces lists and maps as first-class values for variables, in addition to string values which were previously available. However, there was previously no way to override the default value of a list or map, and the functionality for overriding specific map keys was broken. Using the environment variable method for setting variable values, there was previously no way to give a variable a value of a list or map. These now support HCL for individual values - specifying: TF_VAR_test='["Hello", "World"]' will set the variable `test` to a two-element list containing "Hello" and "World". Specifying TF_VAR_test_map='{"Hello = "World", "Foo" = "bar"}' will set the variable `test_map` to a two-element map with keys "Hello" and "Foo", and values "World" and "bar" respectively. The same logic is applied to `-var` flags, and the file parsed by `-var-files` ("autoVariables"). Note that care must be taken to not run into shell expansion for `-var-` flags and environment variables. We also merge map keys where appropriate. The override syntax has changed (to be noted in CHANGELOG as a breaking change), so several tests needed their syntax updating from the old `amis.us-east-1 = "newValue"` style to `amis = "{ "us-east-1" = "newValue"}"` style as defined in TF-002. In order to continue supporting the `-var "foo=bar"` type of variable flag (which is not valid HCL), a special case error is checked after HCL parsing fails, and the old code path runs instead.	10 years ago
James Bardin	2712328d5a	Merge pull request #7756 from hashicorp/jbardin/tf-atlas-version ... core: send version info to atlas	10 years ago
James Bardin	885935962c	Add a terraform version header to all atlas calls ... Using the DefaultHeader added to the atlas.Client	10 years ago
David Glasser	50959a654c	command: Remove second DefaultDataDirectory const (#7666)	10 years ago
James Nugent	3735140286	core: Don't set variables for Atlas until lib is updated	10 years ago
James Nugent	5d18f41f04	core: Convert context vars to map[string]interface{} ... This is the first step in allowing overrides of map and list variables. We convert Context.variables to map[string]interface{} from map[string]string and fix up all the call sites.	10 years ago
Raphael Randschau	9081cabd6e	Add scaleway provider (#7331) ... * Add scaleway provider this PR allows the entire scaleway stack to be managed with terraform example usage looks like this: ``` provider "scaleway" { api_key = "snap" organization = "snip" } resource "scaleway_ip" "base" { server = "${scaleway_server.base.id}" } resource "scaleway_server" "base" { name = "test" # ubuntu 14.04 image = "aecaed73-51a5-4439-a127-6d8229847145" type = "C2S" } resource "scaleway_volume" "test" { name = "test" size_in_gb = 20 type = "l_ssd" } resource "scaleway_volume_attachment" "test" { server = "${scaleway_server.base.id}" volume = "${scaleway_volume.test.id}" } resource "scaleway_security_group" "base" { name = "public" description = "public gateway" } resource "scaleway_security_group_rule" "http-ingress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "inbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } resource "scaleway_security_group_rule" "http-egress" { security_group = "${scaleway_security_group.base.id}" action = "accept" direction = "outbound" ip_range = "0.0.0.0/0" protocol = "TCP" port = 80 } ``` Note that volume attachments require the server to be stopped, which can lead to downtimes of you attach new volumes to already used servers * Update IP read to handle 404 gracefully * Read back resource on update * Ensure IP detachment works as expected Sadly this is not part of the official scaleway api just yet * Adjust detachIP helper based on feedback from @QuentinPerez in https://github.com/scaleway/scaleway-cli/pull/378 * Cleanup documentation * Rename api_key to access_key following @stack72 suggestion and rename the provider api_key for more clarity * Make tests less chatty by using custom logger	10 years ago
James Nugent	b4048dfc1d	core: Add -json flag to `terraform output` ... This commit removes the ability to index into complex output types using `terraform output a_list 1` (for example), and adds a `-json` flag to the `terraform output` command, such that the output can be piped through a post-processor such as jq or json. This removes the need to allow arbitrary traversal of nested structures. It also adds tests of human readable ("normal") output with nested lists and maps, and of the new JSON output.	10 years ago
James Nugent	ef3aad1231	core: Correctly format nested outputs ... This commit pretty prints outputs which consist of nested complex structures (e.g. lists of lists, lists of maps). Fixes #7143.	10 years ago
James Nugent	1ca51ab454	Merge pull request #7589 from hashicorp/b-data-source-plan-counts ... command: Do not count data sources in plan totals	10 years ago
Derek Abdine	7bdc060d24	provider/logentries: Implementing logentries provider (#7067) ... * logentries provider * logentries vendoring * logentries docs	10 years ago
Paul Hinze	d5a941a0a4	command: Do not count data sources in plan totals ... Fixes #7483	10 years ago
James Bardin	b0b2923027	Merge pull request #7443 from hashicorp/jbardin/GH-7264 ... core: Use -state-out option when applying from a plan	10 years ago
James Bardin	6b5ee73e86	Use -state-out option when applying from a plan ... When working from an existing plan, we weren't setting the PathOut field for a LocalState. This required adding an outPath argument to the StateFromPlan function to avoid having to introspect the returned state.State interface to find the appropriate field. To test we run a plan first and provide the new plan to apply with `-state-out` set.	10 years ago
James Bardin	db83a779ab	Fix plan output for data sources ... Data sources are given a special plan output when the diff would show it creating a new resource, to indicate that there is only a logical data resource being read. Data sources nested in modules weren't formatted in the plan output in the same way. This checks for the "data." part of the path in nested modules, and adds acceptance tests for the plan output.	10 years ago
James Nugent	b190aa05a5	core: Add missing OutputStates in synthetic state ... In cases where we construct state directly rather than reading it via the usual methods, we need to ensure that the necessary maps are initialized correctly.	10 years ago
James Nugent	aa5dc453ee	cli: Fix registration of `state mv`. ... Fixes #7259.	10 years ago
James Nugent	75ab4a9970	core: Fix crash with tainted resource ... This commit fixes a crash in `terraform show` where there is no primary resource, but there is a tainted resource, because of the changes made to tainted resource handling in 0.7.	10 years ago
James Nugent	7aec98237c	core: Format empty lists and maps in output ... `terraform output` and it's brethren now consolidate empty maps and lists on a single line of output instead of the pathological behaviour of taking three lines previously. The same code paths are used across all output mechanisms: ``` $ cat main.tf variable "emptystring" { type = "string" default = "" } variable "emptylist" { type = "list" default = [] } variable "emptymap" { type = "map" default = {} } output "emptystring" { value = "${var.emptystring}" } output "emptylist" { value = "${var.emptylist}" } output "emptymap" { value = "${var.emptymap}" } $ terraform apply Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: emptylist = [] emptymap = {} emptystring = $ terraform output emptylist = [] emptymap = {} emptystring = $ terraform show Outputs: emptylist = [] emptymap = {} emptystring = ```	10 years ago
Paul Hinze	1a0893ddc7	command/plan: remove -backup from help text ... The `-backup` flag no longer applies since `terrafom plan` does not write state. Fixes #7087	10 years ago
Maxime Bury	c98f391bee	Add basic implementation for remote state on azure (#7064) ... * Add basic implementation for remote state on azure * Don't auto-provision the container * Fix compilation errors * Add factory to the remote map * Add documentation * Add acceptance tests	10 years ago
James Nugent	c96a8d5302	core: Update `terraform show` to deal with lists ... Fixes #6931.	10 years ago
Matt Morrison	cbfb4d8b86	remote state: Add GCS provider for remote state	10 years ago
Chris Marchesi	9d7fb89114	core: Adding Sensitive attribute to resource schema ... This an effort to address hashicorp/terraform#516. Adding the Sensitive attribute to the resource schema, opening up the ability for resource maintainers to mark some fields as sensitive. Sensitive fields are hidden in the output, and, possibly in the future, could be encrypted.	10 years ago
James Nugent	5a0f6565d3	Merge pull request #6672 from apparentlymart/random-provider ... Logical Resources for Random Values	10 years ago
Sander van Harmelen	d97b24e3c1	Add tests and fix last issues	10 years ago
Sander van Harmelen	8560f50cbc	Change taint behaviour to act as a normal resource ... This means it’s shown correctly in a plan and takes into account any actions that are dependant on the tainted resource and, vice verse, any actions that the tainted resource depends on. So this changes the behaviour from saying this resource is tainted so just forget about it and make sure it gets deleted in the background, to saying I want that resource to be recreated (taking into account the existing resource and it’s place in the graph).	10 years ago
Paul Hinze	aee1520ac5	core: Make refresh message explicitly point out lack of state persist ... Helps make clear to users that refresh only occurs in-memory during plan per @jen20's recommendation	10 years ago
Paul Hinze	ae73aa2fb4	core: Do not persist state after plans ... This makes the behavior of plans much more predictable, as they no longer potentially have side effects on shared remote state.	10 years ago
James Nugent	28ad394264	build: Update generated internal plugin list	10 years ago
James Nugent	8e732c104b	core: Error over panic if output type unknown	10 years ago
James Nugent	3ea3c657b5	core: Use OutputState in JSON instead of map ... This commit forward ports the changes made for 0.6.17, in order to store the type and sensitive flag against outputs. It also refactors the logic of the import for V0 to V1 state, and fixes up the call sites of the new format for outputs in V2 state. Finally we fix up tests which did not previously set a state version where one is required.	10 years ago
Martin Atkins	3e34ddbf38	New "random" provider, representing randomness ... This provider will have logical resources that allow Terraform to "manage" randomness as a resource, producing random numbers on create and then retaining the outcome in the state so that it will remain consistent until something explicitly triggers generating new values. Managing randomness in this way allows configurations to do things like random distributions and ids without causing "perma-diffs".	10 years ago
Martin Atkins	2ca10ad962	command: Show data source reads differently in plans ... Internally a data source read is represented as a creation diff for the resource, but in the UI we'll show it as a distinct icon and color so that the user can more easily understand that these operations won't affect any real infrastructure. Unfortunately by the time we get to formatting the plan in the UI we only have the resource names to work with, and can't get at the original resource mode. Thus we're forced to infer the resource mode by exploiting knowledge of the naming scheme.	10 years ago
Martin Atkins	bfee4b0295	command: don't show old values for create diffs in plan ... New resources logically don't have "old values" for their attributes, so showing them as updates from the empty string is misleading and confusing. Instead, we'll skip showing the old value in a creation diff.	10 years ago
Martin Atkins	5d27a5b3e2	command: Show id only when refreshing managed resources ... Data resources don't have ids when they refresh, so we'll skip showing the "(ID: ...)" indicator for these. Showing it with no id makes it look like something is broken.	10 years ago
Martin Atkins	60c24e3319	command: Prevent data resources from being tainted ... Since the data resource lifecycle contains no steps to deal with tainted instances, we must make sure that they never get created. Doing this out in the command layer is not the best, but this is currently the only layer that has enough information to make this decision and so this simple solution was preferred over a more disruptive refactoring, under the assumption that this taint functionality eventually gets reworked in terms of StateFilter anyway.	10 years ago
Mitchell Hashimoto	b728f8c018	terraform: import state ID should be sent to hook	10 years ago
Mitchell Hashimoto	f6a59734ef	command: UI for import	10 years ago
Mitchell Hashimoto	d6c059c43e	command/import: tests passing	10 years ago
Mitchell Hashimoto	3c9a92e04a	command: Context buliding allows empty module trees	10 years ago