b781e07261
Update CHANGELOG.md
2016-10-14 14:32:41 -04:00
4baed414e7
Merge pull request #9361 from hashicorp/b-interp-multi
...
terraform: multi-var interpolation should use state for count
2016-10-14 11:13:33 -07:00
229be895b1
Update CHANGELOG.md
2016-10-14 10:22:33 -07:00
bed491205a
Merge pull request #9372 from hashicorp/b-update-hil
...
vendor: update HIL to support more eval in indexes, implicit conversion
2016-10-14 10:21:24 -07:00
e678222d56
vendor: update HIL to support more eval in indexes, implicit conversion
2016-10-14 10:13:50 -07:00
c7c31677d9
Merge pull request #9371 from cwood/cwood/fix-sidebar-missing-bitbucket
...
Bitbucket missing from sidebar of providers link.
2016-10-14 11:59:44 -05:00
a8c154b8f8
Bitbucket missing from sidebar of providers link.
2016-10-14 09:55:20 -07:00
d9542be43f
release: clean up after v0.7.6
2016-10-14 16:43:48 +00:00
754bdda8a7
v0.7.6
2016-10-14 16:32:43 +00:00
f98841daa5
Update CHANGELOG.md
2016-10-14 11:03:51 -05:00
afe2d7b65b
Merge pull request #7320 from dtolnay/conflict
...
core: Allow refresh of local state with no resources
2016-10-14 11:00:46 -05:00
728a1e5448
terraform: multi-var interpolation should use state for count
...
Related to #5254
If the count of a resource is interpolated (i.e. `${var.c}`), then it
must be interpolated before any splat variable using that resource can
be used (i.e. `type.name.*.attr`). The original fix for #5254 is to
always ensure that this is the case.
While working on a new apply builder based on the diff in
`f-apply-builder`, this truth no longer always holds. Rather than always
include such a resource, I believe the correct behavior instead is to
use the state as a source of truth during `walkApply` operations.
This change specifically is scoped to `walkApply` operation
interpolations since we know the state of any multi-variable should be
available. The behavior is less clear for other operations so I left the
logic unchanged from prior versions.
2016-10-13 17:57:11 -07:00
fecc218505
Update CHANGELOG.md
2016-10-13 16:06:32 -04:00
c5f85f9a91
Merge pull request #9356 from hashicorp/jbardin/TF-9337
...
Filter nil Deposed values during State init
2016-10-13 16:03:23 -04:00
95786c5090
update copystructure
2016-10-13 15:56:33 -04:00
6721a8ae78
Update CHANGELOG.md
2016-10-13 14:20:01 -05:00
46ee2ef51a
Merge pull request #6819 from hashicorp/f-aws-vpc-data-sources
...
provider/aws: data sources for AWS network planning
2016-10-13 14:17:55 -05:00
25e38f8e72
Update CHANGELOG.md
2016-10-13 15:10:46 -04:00
4f91507d05
Merge pull request #9268 from hashicorp/jbardin/hcl-maps
...
Get rid of the list when parsing HCL maps for vars
2016-10-13 14:18:29 -04:00
7149894e41
Merge pull request #9340 from hashicorp/jbardin/key_file
...
Remove deprecated key_file and bastion_key_file
2016-10-13 14:08:09 -04:00
95d6f29948
Merge pull request #9263 from hashicorp/jbardin/var-numbers
...
Don't parse a TestFlagTypedKV value as a number
2016-10-13 14:07:46 -04:00
cdddc3774a
Merge pull request #9348 from nicksantamaria/upgrade-docs-07-remote-state
...
Added 0.7 upgrade documentation for remote state references.
2016-10-13 12:49:55 -05:00
816c04309c
Filter nil Deposed values during State init
...
The Deposed slice wasn't being normalized and nil values could be read
in from a state file. Filter out the nils during init. There is
still a bug in copystructure, but that will be addressed separately.
2016-10-13 13:46:40 -04:00
86863c6d50
Merge pull request #9355 from mrwacky42/go-version-bump
...
Require Go 1.7
2016-10-13 12:02:15 -05:00
f578e319c3
Require Go 1.7
2016-10-13 09:58:59 -07:00
dc48543e64
Update CHANGELOG.md
2016-10-13 11:23:10 -05:00
04b7950e15
Merge pull request #9346 from hashicorp/b-aws-vpn-connection-retry
...
provider/aws: Poll to confirm delete of resource_aws_customer_gateway
2016-10-13 11:22:43 -05:00
6edbe2faf3
Removed errant backtick in AWS provider documentation. ( #9317 )
2016-10-13 08:50:46 -07:00
fe4799bd68
Add failing test for nil IsntanceState in State
...
A nil InstanceState within State/Modules/Resources/Deposed will panic
during a deep copy. The panic needs to be fixed in copystructure, but
the nil probably should have been normalized out before we got here too.
2016-10-13 11:16:03 -04:00
ad314118a6
Merge #9327 : github_repository resource
2016-10-13 08:15:37 -07:00
e914db2385
website: github_team_repository purpose clarification
...
With the addition of github_repository it may be confusing that
github_team_repository only creates relationships, rather than creating
actual repositories. To reduce the chance of confusion, we'll make this
explicit in the docs for github_team_repository.
Also taking this opportunity to make the examples consistent with what
would be produced by hclfmt.
2016-10-13 08:04:18 -07:00
78c39c7c62
website: docs for github_repository resource
2016-10-13 08:04:18 -07:00
f4ecf72125
provider/github: github_repository resource
...
Allows creation of repositories within the organization configured on the
provider.
2016-10-13 08:04:17 -07:00
52a4086a60
Fixed grammatical error.
2016-10-13 14:10:32 +11:00
14e5c2d3f2
Added 0.7 upgrade documentation for remote state references.
2016-10-13 14:01:02 +11:00
b2b886db43
provider/aws: Poll to confirm delete of resource_aws_customer_gateway
2016-10-12 17:41:03 -05:00
7e0408293f
update CHANGELOG.md
2016-10-12 16:32:14 -04:00
3e99f1a406
Merge pull request #9343 from hashicorp/jbardin/hil
...
Update github.com/hashicorp/hil
2016-10-12 16:29:20 -04:00
86715617ec
Update github.com/hashicorp/hil
...
includes fix for #9282
2016-10-12 16:24:51 -04:00
7c179ba256
Update CHANGELOG.md
2016-10-12 15:19:56 -05:00
7385fa9eac
provider/aws: Support refresh of EC2 instance user_data.
...
Make sure to hash base64 decoded value since user_data might be given
either raw bytes or base64 value.
This helps https://github.com/hashicorp/terraform/issues/1887 somewhat
as now you can:
1) Update user_data in AWS console.
2) Respectively update user_data in terraform code.
3) Just refresh terraform state and it should not report any changes.
2016-10-12 15:19:25 -05:00
961c8f9d97
Merge pull request #9341 from davewalter/master
...
Update the docs for the AWS security_group_rule resource.
2016-10-12 14:50:47 -05:00
5a40fa2914
Update the docs for the AWS security_group_rule resource.
...
- clarify the description of the from/to port arguments
2016-10-12 12:24:45 -07:00
647d682348
Remove key_file from docs as well
2016-10-12 14:48:15 -04:00
8174037a2b
Remove deprecated key_file and bastion_key_file
...
These were deprecated in the 0.6.x series. Their functionality was broken
in a recent release which whould have removed them as well.
2016-10-12 14:30:09 -04:00
77d76a69ba
provider/aws: Bump Directory Service creation timeout to 45m
2016-10-12 09:47:39 -05:00
9c3084b2af
Update CHANGELOG.md
2016-10-11 15:39:22 -05:00
ed37eae52b
[AWS] Retry setTags operation
2016-10-11 15:38:25 -05:00
f2c95cd5be
Update CHANGELOG.md
2016-10-11 15:35:44 -05:00
be523d3792
Fixes #6076 - Adjusts check to allow for instance-id reset on aws_route
2016-10-11 15:35:03 -05:00
James Bardin