Commit Graph

15500 Commits

Author SHA1 Message Date
pbthorste 11f680a88e remove computed true for postgres connections 2017-01-11 22:55:50 +01:00
pbthorste 0c1175f78b set default postgres connection limit 2017-01-11 22:45:30 +01:00
Jake Champlin 1f036e7743 Update CHANGELOG.md 2017-01-11 13:39:26 -05:00
Jake Champlin ed275af697 Merge pull request #11157 from hashicorp/b-add-id-route-table
provider/aws: Add missing id argument for Route Table data source
2017-01-11 13:38:02 -05:00
Jake Champlin 642e0107e1
Update error message to 'route_table_id' 2017-01-11 13:23:40 -05:00
Jake Champlin 439b94707e
Use 'route_table_id' instead of 'rtb_id' 2017-01-11 13:22:29 -05:00
Jake Champlin d794bdfc26
provider/aws: Add missing id argument for Route Table data source
Documentation for the `aws_route_table` data source mentions that it supports a route table `id` as an argument, however it was missing from the actual provider code.

Adds in the missing provider code, adds a test, and updates the documentation to use `rtb_id` as the argument, instead of the more ambiguous `id`.
2017-01-11 13:16:52 -05:00
Jake Champlin ec7fdab16d Update CHANGELOG.md 2017-01-11 12:54:41 -05:00
Jake Champlin 0f93af0fb0 Update CHANGELOG.md 2017-01-11 12:54:27 -05:00
Jake Champlin 3de923d13f Merge pull request #11152 from hashicorp/b-aws-route-table-11134
provider/aws: Fix panic caused by main route table lookup
2017-01-11 12:51:28 -05:00
Jake Champlin 7399401b64
provider/aws: Fix panic caused by main route table lookup
A VPC's main route table has an implicit subnet association, not an explicit subnet association. This caused a Terraform panic when using the `data_source_aws_route_table` resource to query the main route table for a VPC.

This fixes the Terraform panic, and allows the data lookup to complete successfully. Also added an acceptance test to verify the bugfix.

Fixes: #11134
2017-01-11 12:33:15 -05:00
clint f895f93769 release: clean up after v0.8.4 2017-01-11 17:21:31 +00:00
clint a791ff09b2
v0.8.4 2017-01-11 17:03:56 +00:00
Clint 3ba10a2c63 Merge pull request #11153 from hashicorp/catsby-patch-1
Update CHANGELOG.md with BC for v0.8.4
2017-01-11 10:42:16 -06:00
Clint 7300634cf0 Update CHANGELOG.md 2017-01-11 10:41:44 -06:00
Clint 8f27342266 Update CHANGELOG.md
BC note on the Arukas provider
2017-01-11 10:40:39 -06:00
Clint c629145120 Merge pull request #11149 from hashicorp/revert-arukas
Revert "New provider arukas (#10862)"
2017-01-11 10:35:01 -06:00
clint shryock 87bb691800 Revert "New provider arukas (#10862)"
This reverts commit 9176bd4861.
This provider includes a dependency that at time of writing requires a
*nix system, and will not build on Windows.
2017-01-11 09:04:32 -06:00
Clint 553dc74a88 Merge pull request #11146 from hashicorp/b-make-windows
Build for Windows in Travis
2017-01-11 09:04:02 -06:00
clint shryock ce0fa85405 just us GOOS 2017-01-11 08:53:28 -06:00
clint shryock f4f9af3bee build on windows 2017-01-11 08:32:16 -06:00
Simon McCartney 97d59f55ed Corrected typo s/OpenStack/OpsGenie/ (#11141) 2017-01-11 10:38:04 +00:00
clint shryock 6bafd4c896 fix typo 2017-01-10 11:06:51 -06:00
Jake Champlin d8e8f13fd7 Merge pull request #11132 from hashicorp/b-fix-digitalocean-droplet-resize-acctest
provider/digitalocean: Fix failing acceptance test
2017-01-10 10:55:10 -05:00
Jake Champlin 712b3e74b6
provider/digitalocean: Fix failing acceptance test
The second step of the `TestAccDigitalOceanDroplet_ResizeWithOutDisk` acceptance test was regularly failing. Upon investigation it was found that the second step's Terraform configuration had omitted the `user_data` parameter, thus forcing Terraform to create a new droplet resource instead of updating the current resource.

```
-/+ digitalocean_droplet.foobar
    disk:                 "20" => "<computed>"
    image:                "centos-7-x64" => "centos-7-x64"
    ipv4_address:         "138.197.0.55" => "<computed>"
    ipv4_address_private: "" => "<computed>"
    ipv6_address:         "" => "<computed>"
    ipv6_address_private: "" => "<computed>"
    locked:               "false" => "<computed>"
    name:                 "foo" => "foo"
    region:               "nyc3" => "nyc3"
    resize_disk:          "true" => "false"
    size:                 "512mb" => "1gb"
    ssh_keys.#:           "1" => "1"
    ssh_keys.0:           "5770472" => "5770472"
    status:               "active" => "<computed>"
    user_data:            "foobar" => "" (forces new resource)
    vcpus:                "1" => "<computed>"
```

This fixes the acceptance test by adding the missing `user_data` parameter.
2017-01-10 10:00:04 -05:00
Ninir fe60b4e90a Added aws-sdk-go SFN service (#11109) 2017-01-10 14:17:39 +00:00
stack72 288996f69c release: clean up after v0.8.3 2017-01-10 09:10:37 +00:00
stack72 b845cb7093
v0.8.3 2017-01-10 09:03:50 +00:00
Paul Stack 2b16338643 Update CHANGELOG.md 2017-01-10 08:52:09 +00:00
Peter McAtominey 825a41aa08 provider/azurerm: fix update protocol for lb_probe (#11125)
request_path had Computed enabled which prevented updating it to an empty value

TF_ACC=1 go test ./builtin/providers/azurerm -v -run TestAccAzureRMLoadBalancerProbe -timeout 120m
=== RUN   TestAccAzureRMLoadBalancerProbe_basic
--- PASS: TestAccAzureRMLoadBalancerProbe_basic (119.63s)
=== RUN   TestAccAzureRMLoadBalancerProbe_removal
--- PASS: TestAccAzureRMLoadBalancerProbe_removal (122.50s)
=== RUN   TestAccAzureRMLoadBalancerProbe_update
--- PASS: TestAccAzureRMLoadBalancerProbe_update (129.98s)
=== RUN   TestAccAzureRMLoadBalancerProbe_duplicate
--- PASS: TestAccAzureRMLoadBalancerProbe_duplicate (115.22s)
=== RUN   TestAccAzureRMLoadBalancerProbe_updateProtocol
--- PASS: TestAccAzureRMLoadBalancerProbe_updateProtocol (127.25s)
PASS
ok  	github.com/hashicorp/terraform/builtin/providers/azurerm	614.657s
2017-01-10 08:49:30 +00:00
Paul Stack 2afc0c49ce Update CHANGELOG.md 2017-01-09 23:16:45 +00:00
Paddy 690db74d4a Read update_strategy before overwriting it. (#11013)
As brought up in #10174, our update_strategy property for instance group
managers in GCP would always be set to "RESTART" on read, even if the
user asked for them to be "NONE" in the config.

This adds a test to ensure that the user wishes were respected, which
fails until we check for update_strategy in the ResourceData before we
update it within the Read function. Because the update_strategy property
doesn't map to anything in the API, we never need to read it from
anywhere but the config, which means the ResourceData should be
considered authoritative by the time we get to the Read function.

The fix for this was provided by @JDiPierro in #10198 originally, but
was missing tests, so it got squashed into this.
2017-01-09 23:15:50 +00:00
Paul Stack a8ce9272e4 Update CHANGELOG.md 2017-01-09 23:12:44 +00:00
Clint c0d0f711d9 provider/aws: Allow disabled access_log in ELB (#11120)
* provider/aws: Save disabled ELB accesslogs to state

Save any explicitly disabled access_log to state. Do not save disabled
access_logs if they are not in the configuration.

* test that fails on master
2017-01-09 23:10:58 +00:00
Jake Champlin 5a9a44a36e Update CHANGELOG.md 2017-01-09 16:26:19 -05:00
Jake Champlin b4053dcdc6 Merge pull request #11119 from hashicorp/b-aws-route53-11114
provider/aws: Route53 Record: Add Type validation
2017-01-09 16:18:39 -05:00
Jake Champlin 1955ac38bc
provider/aws: Route53 Record: Add Type validation
Adds validation for the `type` parameter of an `aws_route53_record` resource.

This will allow Terraform to catch any user errors of a `type` parameter during a `terraform plan` instead of during a `terraform apply`.

Fixes: #11114
2017-01-09 15:45:26 -05:00
Paul Stack 64d57e3553 Update CHANGELOG.md 2017-01-09 19:18:46 +00:00
Paul Stack 519d873263 provider/aws: New Resource aws_codedeploy_deployment_config (#11062)
* provider/aws: New Resource - aws_codedeploy_deployment_config

* provider/aws: Adding acceptance tests for new
aws_codedeploy_deployment_config resource

* provider/aws: Documentation for the aws_codedeploy_deployment_config resource

* Update codedeploy_deployment_config.html.markdown
2017-01-09 19:17:09 +00:00
Paul Stack 2c67ee7fde Update CHANGELOG.md 2017-01-09 19:12:38 +00:00
Paul Stack 5ece0f2d04 provider/aws: aws_db_instance restored from snapshot had problem with (#11050)
subnet_group

Fixes #11024

A change was introduced in 0.8.2 that allows db_instances to change
their db_subnet_group. Unfortunately, this caused an issue for
db_instances that were being restored from snapshot. The restore from
snapshot part of create calls the Update func whereas a normal create
calls the Read func

When calling the Update func, the db_instance was trying to go through a
db_subnet_group_name change and was failing for the following reason:

```
InvalidVPCNetworkStateFault: You cannot move DB instance _rds_instance_name_ to subnet group _subnet_group_name_. The specified DB subnet group and DB instance are in the same VPC. Choose a DB subnet group in different VPC than the specified DB instance and try again.
```
2017-01-09 19:10:13 +00:00
Mitchell Hashimoto e9bb92b5f3 Update CHANGELOG.md 2017-01-09 10:08:59 -08:00
Paul Stack 9095f9d110 Update CHANGELOG.md 2017-01-09 17:19:09 +00:00
Kazumichi Yamamoto 9176bd4861 New provider arukas (#10862)
* Add a Arukas provider

* Add dependencies for the Arukas provider

* Add documents for the Arukas
2017-01-09 17:14:33 +00:00
Mitchell Hashimoto 08728d9366 Merge pull request #11095 from hashicorp/b-dot-opts-nil
dag: string DotOpts through to vertex
2017-01-09 09:11:40 -08:00
Mitchell Hashimoto 7f35b2015c Merge pull request #11099 from hashicorp/b-root-module
config/module: disallow root modules named "root"
2017-01-09 09:11:10 -08:00
Jake Champlin f941eddbea Update CHANGELOG.md 2017-01-09 12:03:20 -05:00
Jake Champlin d883f32602 Merge pull request #11116 from hashicorp/f-s3-bucket-name-validation
provider/aws: Add S3 Bucket name validation
2017-01-09 12:01:26 -05:00
Jake Champlin b9d4a54341
provider/aws: Add S3 Bucket name validation
Adds region specific S3 bucket name validation. Currently all regions except for us-east-1 force a dns-compliant naming convention. Thus we cannot utilize the standard `SchemaValidateFunc` interface to validate an S3 bucket name.
 This change creates a helper function outside of the schema validation interface so we can validate S3 bucket names for both naming conventions. At a later date, when the us-east-1 region is updated to conform to a dns-compliant naming scheme, we can refactor the `validateS3BucketName` function to fit the `SchemaValidateFunc` interface.
2017-01-09 11:22:47 -05:00
Gerrit Tamboer e0ac63beb9 Remove key.name from example, deprecated since 0.7 (#11079) 2017-01-09 16:07:36 +00:00