Commit Graph

14635 Commits

Author SHA1 Message Date
Paul Stack 3782fefd3e Update CHANGELOG.md 2016-11-17 14:04:03 +02:00
Andrew Garrett 3822c69995 Add name_prefix to aws_iam_policy (#10178)
This is intended to behave the same way as name_prefix does in
aws_iam_role.

Fixes #10176
2016-11-17 14:03:03 +02:00
James Turnbull 86b7333a1f Fixed some typos and formatting in AWS index docs (#10189)
* Fixed whitespace

* Fixed some typos and formatting in AWS index docs
2016-11-17 13:52:06 +02:00
Paul Stack 3774b162f2 Merge pull request #10190 from jamtur01/console
Minor fixes to the console docs
2016-11-17 13:45:10 +02:00
James Turnbull f7e23360bd Fixed formatting 2016-11-17 05:33:02 -05:00
James Turnbull e34be68633 Added exit command mention 2016-11-17 04:23:50 -05:00
James Bardin 8f6811da0c Add failing test for GH-10155
Overriding a map variable with the incorrect type panics
2016-11-16 18:20:59 -05:00
Clint 81125f6aeb Update CHANGELOG.md 2016-11-16 13:45:29 -06:00
Clint d004a24659 Merge pull request #10171 from Ninir/vpc_enable_dns_support
provider/aws: Fixed the aws_vpc enable_dns_support handling on creation
2016-11-16 13:41:35 -06:00
James Bardin 50ecb746ec Merge pull request #10170 from hashicorp/jbardin/no-darwin-386
Remove darwin/386 from the build
2016-11-16 14:06:33 -05:00
Ninir 281eba72ad provider/aws: Fixed the aws_vpc enable_dns_support handling on creation 2016-11-16 20:05:49 +01:00
James Bardin f85232a239 Remove darwin/386 from the build
There isn't a supported configuration that runs darwin/386, so remove it
from the build.
2016-11-16 13:46:57 -05:00
Paul Stack 789b660b32 Update CHANGELOG.md 2016-11-16 19:19:17 +02:00
Mitchell Hashimoto 06b95b3c00 release: clean up after v0.8.0-beta2 2016-11-16 17:14:31 +00:00
Mitchell Hashimoto 7e4385ea2f v0.8.0-beta2 2016-11-16 17:13:31 +00:00
Paul Stack e319d2cd59 Merge pull request #10105 from hashicorp/f-chef-key_material
provider/chef: Migrate Chef to use KEY_MATERIAL rather than using a Pem file
2016-11-16 19:12:28 +02:00
stack72 50cab912af
provider/chef: Migrate Chef to use KEY_MATERIAL rather than using a Pem
file

This will allow us to standardise on how we set KEY_MATERIAL
2016-11-16 19:03:37 +02:00
Paul Stack 7293630f64 Merge pull request #10140 from jjasghar/patch-1
Update index.html.markdown
2016-11-16 09:22:30 +02:00
Paul Stack 7aab812750 Merge pull request #10145 from jrnt30/explicit-elb-defaults
Doc Update for ELB defaults
2016-11-16 09:19:35 +02:00
James Bardin e28e11d44c Fix resource.UniqueId to be properly ordered
UniqueId attempted to provide an ordered unique id by using a nanosecond
timestamp, but doesn't take into account that time is not monotonic
increasing. This provides an implementation that will always be
increasing.
2016-11-15 21:58:23 -05:00
Mitchell Hashimoto db49d52889
update CHANGELOG 2016-11-15 15:36:09 -08:00
Mitchell Hashimoto 20e3ae3aa7 Merge pull request #10150 from hashicorp/update-hil
vendor: update HIL
2016-11-15 15:32:38 -08:00
Mitchell Hashimoto 8fab86a9d4
website: update docs for precedence rules 2016-11-15 15:29:38 -08:00
Mitchell Hashimoto 9daa9942b3
vendor: update HIL 2016-11-15 15:24:48 -08:00
Paddy ed2fd5ab1f release: clean up after v0.7.11 2016-11-15 22:26:09 +00:00
James Bardin 3df3b99276 Make sure each GraphBuilder has a Name
Ensure that each instance of BasucGraphBuilder gets a name corresponding
to the Builder which created it. This allows us to differentiate the
graphs in the logs.
2016-11-15 16:40:10 -05:00
Justin Nauman 75257e13ab Doc Update for ELB defaults
- Doc update to explicitly call out ELB defaults (so I don't have to look
at the source again :)
2016-11-15 15:00:13 -06:00
Mitchell Hashimoto 5eaeb0f89f Update CHANGELOG.md 2016-11-15 11:56:14 -08:00
Mitchell Hashimoto ea2c084176 Merge pull request #10141 from hashicorp/revert-9118-spew-diff-mismatch
Revert "[WIP] core: Log diff mismatch using spew instead of %#v"
2016-11-15 11:53:37 -08:00
Mitchell Hashimoto b72ef90c2f Revert "[WIP] core: Log diff mismatch using spew instead of %#v" 2016-11-15 11:53:28 -08:00
Mitchell Hashimoto b20f43834b Merge pull request #9118 from hashicorp/spew-diff-mismatch
[WIP] core: Log diff mismatch using spew instead of %#v
2016-11-15 11:53:19 -08:00
Mitchell Hashimoto 97943acbf8 Merge pull request #10139 from hashicorp/b-schema-diff-destroy
helper/schema: mark diff as forcenew if element is computed
2016-11-15 11:50:12 -08:00
JJ Asghar 07c80ef09d Update index.html.markdown
Added a note about self-signed certs and vsphere.
2016-11-15 13:49:01 -06:00
Mitchell Hashimoto 55ef93f0f9
terraform: Diff.Same should understand that Destroy might go false 2016-11-15 11:26:42 -08:00
Mitchell Hashimoto 39542898b0
helper/schema: mark diff as forcenew if element is computed
Fixes #10125

If the elements are computed and the field is ForceNew, then we should
mark the computed count as potentially forcing a new operation.

Example, assuming `groups` forces new...

**Step 1:**

    groups = ["1", "2", "3"]

At this point, the resource isn't create, so this should result in a
diff like:

    CREATE resource:
      groups: "" => ["1", "2", "3"]

**Step 2:**

    groups = ["${computedvar}"]

The OLD behavior was:

    UPDATE resource
      groups.#: "3" => "computed"

This would cause a diff mismatch because if `${computedvar}` was
different then it should force new. The NEW behavior is:

    DESTROY/CREATE resource:
      groups.#: "3" => "computed" (forces new)
2016-11-15 11:02:14 -08:00
Mitchell Hashimoto 75aabd7a79 Merge pull request #10118 from hashicorp/b-config-race
config: maintain slice index accounting for computed keys
2016-11-15 09:06:12 -08:00
Mitchell Hashimoto dc2c4cc417 Merge pull request #10135 from hashicorp/b-data-info
terraform: EvalInstanceInfo on data sources in new graph
2016-11-15 09:04:05 -08:00
Mitchell Hashimoto c6fd938fb8
terraform: EvalInstanceInfo on data sources in new graph
This doesn't cause any practical issues as far as I'm aware (couldn't
get any test to fail), but caused shadow errors since it wasn't matching
the prior behavior.
2016-11-15 09:02:10 -08:00
Clint 9aef2e5aa8 Update CHANGELOG.md 2016-11-15 11:00:51 -06:00
clint shryock 0369112057 Merge branch 'pr-10113'
* pr-10113:
  Added retry_option for aws_kinesis_firehose_stream redshift_configuration
2016-11-15 10:56:16 -06:00
Ninir 3d56d20d82 Added retry_option for aws_kinesis_firehose_stream redshift_configuration 2016-11-15 10:55:02 -06:00
Mitchell Hashimoto b6f5eb6371 Merge pull request #10134 from hashicorp/b-shadow-close
helper/shadow: Close for auto-closing all values
2016-11-15 08:54:42 -08:00
Mitchell Hashimoto 6557a3de18
helper/shadow: Close for auto-closing all values
Fixes #10122

The simple fix was that we forgot to close `ReadDataApply` for the
provider. But I've always felt that this section of the code was brittle
and I wanted to put in a more robust solution. The `shadow.Close` method
uses reflection to automatically close all values.
2016-11-15 08:54:26 -08:00
James Bardin bb137f4bfb Remove the dot graphs from the debug log,
and record the walk visits in the debug information.
2016-11-15 11:11:53 -05:00
Clint 35f3d46a9d Update CHANGELOG.md 2016-11-15 10:01:02 -06:00
Clint 665ca05bf6 Merge pull request #10112 from Ninir/aws_kinesis_firehose_stream_buffer_option
provider/aws: kinesis_firehose_delivery_stream: Fixed ES buffering_interval option
2016-11-15 09:55:12 -06:00
James Bardin 6d30b60144 Add DebugVisitInfo
This encodes vertex debug information into the graph log when a vertex
is visited during a walk operation. These can ordered to show how the
Graph was walked.

Add a mutex to the encoder so it can be used during a parallel walk.

Moved string literal constants used for marshaling to pre-defined constants.
Did some renaming to make the marshal* structures more consistent.
2016-11-15 10:39:08 -05:00
Clint 4e2865a719 Merge pull request #10131 from jrnt30/increased-db-options-delete
GH-7311 - Increasing deletion timeout wait
2016-11-15 09:27:45 -06:00
James Bardin 23de57ddf3 Merge pull request #10104 from hashicorp/jbardin/debug
DebugOperation
2016-11-15 10:16:08 -05:00
Justin Nauman e36f424af3 GH-7311 - Increasing deletion timeout wait
- Per our discussion around the PR to increase this initially, we
weren't sure if 1 minute would be sufficient.  Well, it turns out it
wasn't for me today (we don't delete these often so not sure how
often people run into this).

Picking another somewhat arbitrary value of 5 minutes in the hopes
that it will be sufficient (today it took a little over 2 minutes).
2016-11-15 09:11:28 -06:00