99ab233740
Fixes an vet error.
2016-05-17 06:23:53 -10:00
592162c92a
Update CHANGELOG.md
2016-05-17 11:13:00 -05:00
faa6ddb2ee
provider/aws: Support for Redshift Cluster encryption using a KMS key ( #6712 )
2016-05-17 11:12:39 -05:00
91a1097041
provider/aws: Randomize key names in KMS alias test
2016-05-17 10:40:42 -05:00
54335be3aa
vendor: Updating Gophercloud dependencies
2016-05-17 13:20:36 +00:00
b204d35e19
provider/openstack openstack_blockstorage_volume_v2 resource
...
This commit adds an openstack_blockstorage_volume_v2 resource. This
resource is able to create volumes using the OpenStack Block Storage
v2 API.
2016-05-17 13:20:26 +00:00
ef3de51199
Include the list of allowed values for AWS auto scaling group termination policies ( #6710 )
...
Ref: http://docs.aws.amazon.com/autoscaling/latest/userguide/as-instance-termination.html#custom-termination-policy
2016-05-17 13:27:33 +01:00
cb8054137b
Merge pull request #6703 from igable/azurerm-custom-image-docs
...
website: docs for azurerm custom images
2016-05-17 01:28:39 -05:00
adf3dcb482
Merge pull request #6696 from josephholsten/rm-dup-columnize
...
Godeps: rm dup github.com/ryanuber/columnize
2016-05-17 01:27:33 -05:00
988c8144c0
website: docs for azurerm custom images
...
Adds docs on booting custom images with the azurerm_virtual_machine
resource; this was previously undocumented.
2016-05-16 18:16:52 -07:00
1bb3c7d016
Merge pull request #6694 from hashicorp/sethvargo/training
...
Add note about paid training
2016-05-16 18:56:12 -05:00
6401344234
Update CHANGELOG.md
2016-05-16 16:49:48 -05:00
e9915d2112
Godeps: rm dup github.com/ryanuber/columnize
2016-05-16 14:36:37 -07:00
0088b33b84
Add note about paid training
2016-05-16 16:45:47 -04:00
f075b0214d
providers/google: Don't fail deleting disks that don't exist.
...
Addresses #5942
2016-05-16 11:57:04 -07:00
a2950c76d9
Merge pull request #6598 from hashicorp/f-data-sources
...
Data-driven Terraform Configuration
2016-05-16 13:00:41 -05:00
f64f470807
providers/aws: fix placement group import
2016-05-16 10:38:53 -07:00
dc3163c464
providers/aws: placement group import
2016-05-16 10:35:44 -07:00
519f0ae4d6
providers/aws: launch configuration import
2016-05-16 10:26:49 -07:00
23340d3c84
provider/aws: Fix crash in ElastiCache param group
2016-05-16 12:20:06 -05:00
a992860b8d
providers/aws: key_pair import
2016-05-16 10:13:20 -07:00
4e3488afb8
providers/aws: customer gateway import
2016-05-16 10:03:57 -07:00
2a30178413
providers/aws: flow log import
2016-05-16 10:03:57 -07:00
f6b77a6c02
providers/aws: import network ACLs
2016-05-16 10:03:57 -07:00
2d5745328b
providers/aws: import main route table association
2016-05-16 10:03:57 -07:00
ab7b5dab2d
providers/aws: route tables import assocations
2016-05-16 10:03:57 -07:00
a1035804d4
providers/aws: route table import should ignore default rule
2016-05-16 10:03:57 -07:00
08b7f67227
providers/aws: route table import
2016-05-16 10:03:57 -07:00
a4e48b19c0
providers/aws ENI import
2016-05-16 10:03:57 -07:00
9cdbed11ff
providers/aws: ebs volume and autoscaling group
2016-05-16 10:03:57 -07:00
884980da1a
providers/aws: instance, nat, internet gateway
2016-05-16 10:03:57 -07:00
830708a882
providers/aws: elb
2016-05-16 10:03:57 -07:00
91938cf55f
providers/aws: resource aws_subnet import
2016-05-16 10:03:57 -07:00
b75d5bb46d
providers/aws: vpc dhcp options
2016-05-16 10:03:57 -07:00
da353c3637
aws/aws_vpc: import
2016-05-16 10:03:57 -07:00
420e13d2f2
providers/aws: eip uses passthrough importstate
2016-05-16 10:03:57 -07:00
b7d4767dd6
helper/schema: pass through import state func
2016-05-16 10:03:57 -07:00
b9d0e14d2a
provider/aws: Update Lambda tests for more random names
2016-05-16 10:31:46 -05:00
fce7aa483d
Add version_id attribute for aws_s3_bucket_object ( #6677 )
2016-05-16 08:49:59 -05:00
ffcf6cf6f7
Merge pull request #6675 from atward/build_check
...
Don't assume dev platform was built
2016-05-15 23:26:12 -05:00
4a29be7b50
Don't assume dev platform was built
2016-05-16 10:00:44 +10:00
76e1a8ffb4
Update CHANGELOG.md
2016-05-14 21:56:18 -05:00
f69d95d01f
Merge pull request #6579 from Fodoj/reassociate-fip-on-update
...
provider/openstack: Reassociate FIP on network changes
2016-05-14 21:55:16 -05:00
94d27ba3ea
Update CHANGELOG.md
2016-05-14 20:46:01 -05:00
b53c74a9ae
Merge pull request #6279 from ZZelle/support-client-cert
...
provider/openstack: Support client certificates
2016-05-14 20:44:57 -05:00
feafc94dde
website: docs for the "random" provider
2016-05-14 16:49:10 -07:00
eec6c88fd2
provider/random: random_shuffle resource
...
random_shuffle takes a list of strings and returns a new list with the
same items in a random permutation.
Optionally allows the result list to be a different length than the
input list. A shorter result than input results in some items being
excluded. A longer result than input results in some items being
repeated, but never more often than the number of input items.
2016-05-14 16:48:45 -07:00
b1de477691
provider/random: random_id resource
...
This resource generates a cryptographically-strong set of bytes and
provides them as base64, hexadecimal and decimal string representations.
It is intended to be used for generating unique ids for resources
elsewhere in the configuration, and thus the "keepers" would be set to
any ForceNew attributes of the target resources, so that a new id is
generated each time a new resource is generated.
2016-05-14 15:26:42 -07:00
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".
2016-05-14 15:26:38 -07:00
453fc505f4
core: Tolerate missing resource variables during input walk
...
Provider nodes interpolate their config during the input walk, but this
is very early and so it's pretty likely that any resources referenced are
entirely absent from the state.
As a special case then, we tolerate the normally-fatal case of having
an entirely missing resource variable so that the input walk can complete,
albeit skipping the providers that have such interpolations.
If these interpolations end up still being unresolved during refresh
(e.g. because the config references a resource that hasn't been created
yet) then we will catch that error on the refresh pass, or indeed on the
plan pass if -refresh=false is used.
2016-05-14 09:25:03 -07:00
John Bresnahan