6bb8947d16
providers/aws: aws_elb incr. idle_timeout to 60s
...
per docs
http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/config-idle-timeout.html
2015-04-23 12:46:52 +03:00
78f9fb164b
provider/aws: fix compilation errors
2015-04-22 08:42:44 +02:00
887f1b3d12
Merge branch 'elb-connection-settings' of https://github.com/jwaldrip/terraform into jwaldrip-elb-connection-settings
2015-04-22 08:38:19 +02:00
81079bb6ac
handle addition/update/removal of listeners after creation
2015-04-21 23:17:17 +01:00
3e6822ce08
more cleans ups of SDK reference
2015-04-16 15:28:18 -05:00
4186ec18c6
providers/aws: Conver AWS ELB to upstream
2015-04-14 16:41:36 -05:00
74bfbece69
Implement Additional ELB Connection Attributes
2015-04-13 14:14:26 -06:00
ef094e2cfe
provider/aws: Add tag support to ELB
2015-03-24 13:37:42 -05:00
580b696e7f
Strike 'goamz' from the repo'
2015-03-12 16:49:38 -05:00
da55f9bf85
provider/aws: Convert AWS ELB to aws-sdk-go
2015-03-02 09:44:06 -06:00
86a2449569
Revert "Merge pull request #804 from PeoplePerHour/f-aws-elb-subnet"
...
Unfortunately, the acceptance tests here were improperly passing, and
allowing Subnet updates on ELBs is not as straightfoward as simply
removing `ForceNew`.
Subnets on ELBs need to be managed by two explicit API calls:
* `AttachLoadBalancerToSubnets` - http://bit.ly/elbattachsubnet
* `DetachLoadBalanceFromSubnets` - http://bit.ly/elbdetachsubnet
We'll need to circle back and use these APIs to explicitly add support.
This fixes the failure of `TestAccAWSELB_AddSubnet` by removing the
test.
This reverts commit 61e91017be49b3afe452
2015-02-18 18:15:04 -06:00
1752c93e0c
update CHANGELOG
2015-02-17 09:44:44 -08:00
9a19eb3110
Merge pull request #721 from robzienert/change-elb-listener-force-new
...
providers/aws: Changing AWS ELB to not ForceNew when listeners change
2015-02-17 09:43:46 -08:00
481b3c7e3b
provider/aws: fix for #915 , disabling ForceNew while updating elb healthchecks
2015-02-06 15:03:52 -08:00
04ac1ffd02
provider/aws: fix for #915 - aws_elb.health_check attributes does not update during update
2015-02-02 19:25:54 -08:00
7759a28e9c
No longer needed after merging of PR 804.
2015-01-21 18:48:28 +11:00
df71834ff7
Merge pull request #831 from gulyasm/log-typo
...
Fixed wrong cross zone balancing error log.
2015-01-20 13:20:25 -08:00
0486dd0624
Fixed wrong cross zone balancing error log.
...
If updating the cross zone balancing in the aws elb resource fails, the
error log claimed that the health check configuration failed. Fixed.
2015-01-17 16:20:35 +01:00
c963793f3d
providers/aws: elb subnet change should not force a new resource
2015-01-15 10:43:26 +02:00
186af0bbb3
Changing AWS ELB to not ForceNew when listeners change
2014-12-27 22:33:33 -06:00
852e2f74ca
Fixing aws_elb schema
...
If not suppling the `availability_zones`, they will be computed
(meaning an update/refresh will retrieve the info and update the values
to the state file).
So without the `Computed = true` the diff will always flag this as a
change, even when it’s not.
2014-12-25 23:12:54 +01:00
b58e468033
Updated the security_group attribute to use a set
...
This way the order returned by the API has no impact on the saved
state, preventing false positives when diffing.
2014-12-17 23:53:01 +01:00
9797881ed8
Updating the tests and refactoring the code a little
...
There was an error in the goamz package the prevented updating the
availability zones correctly. So PR #181 should be merged before this
one can be merged…
2014-12-16 15:21:25 +01:00
3aeba87e38
Updating the resource to use a set instead of a list
...
By using a set for the availability zones, you can use things like
`availability_zones = ["${aws_instance.web.*.availability_zone}"]`
where is very likely multiple of the same zones will be added to the
set. If you use a list here, the list will say it’s changed (even if
you add the same zone) which will force a new resource.
2014-12-16 13:13:59 +01:00
1d3e30b353
enabled cross zone load balancing
2014-12-10 12:49:43 +05:30
eccd5ad308
Refactored about 90%
...
Still need to update 2 resources and check the acceptance tests, but
overall we’re nearly there 😃
2014-11-21 17:58:34 +01:00
590a635b70
providers/aws: ELB should treat subest as a set
2014-10-20 16:32:38 -07:00
7e2a421d87
providers/aws: ELB treats subnets as a set
2014-10-20 13:34:26 -07:00
05bfe85f9f
providers/aws: instances can be computed on an ELB
2014-10-16 18:24:58 -07:00
152d5b0c69
providers/aws: elb properly hashes listeners
2014-10-16 18:02:03 -07:00
51d66b678d
providers/aws: resource ELB listeners [GH-314]
2014-10-10 16:35:52 -07:00
281ba93d39
providers/aws: set the dns_name on create [GH-393]
2014-10-10 13:50:08 -07:00
b43ca0aa52
providers/aws: handle case where ELB is deleted manually [GH-304]
2014-10-10 10:35:34 -07:00
7dcb386e29
providers/aws: fix some computed attributes on ELB
2014-10-10 00:17:35 -07:00
dd2b1fe442
providers/aws: make health checks work
2014-10-10 00:07:08 -07:00
12ff354749
providers/aws: convert most of ELB to schema
2014-10-09 23:58:48 -07:00
d01418270a
Add listener.ssl_certificate_id support to AWS ELB (@jpadvo [GH-176])
2014-10-02 05:19:36 +03:00
6e02465be7
providers/aws: read internal for ELB
2014-09-30 13:37:04 -07:00
09ce13d040
Merge pull request #303 from buth/internalelbs
...
provider/aws: added missing internal ELB option
2014-09-30 13:29:35 -07:00
9b2b3a963f
ResourceDiff => InstanceDiff
2014-09-17 16:33:24 -07:00
90b75b86c4
added missing internal ELB option
2014-09-17 17:56:27 -04:00
c5d6df692d
providers/aws: tests passing, compiles
2014-09-16 17:49:24 -07:00
4cdb95a6b2
Merge pull request #166 from alekstorm/aws-elb-subnets-security-groups
...
Add 'security_groups' and 'subnets' args to 'aws_elb'
2014-08-19 09:40:30 -07:00
8d97c3656c
Add listener.ssl_certificate_id support to AWS ELB
2014-08-10 17:16:53 -07:00
5a84296c61
Add 'security_groups' and 'subnets' args to 'aws_elb'
2014-08-07 17:41:15 -07:00
46154ca1d3
Fixed a ton of typos in docs and comments
2014-08-07 00:19:56 -07:00
7adc6162d8
providers/aws: add test for health check, save health check state
...
cc/ @vertis
I added an acceptance test here, as well as making it so we
saved the health check state on update_state.
2014-07-30 10:15:22 -04:00
0eed0908df
Add health_check to aws_elb resource
2014-07-30 21:46:51 +10:00
7ef47671b0
providers/aws: only security group and instances if we have them
2014-07-27 21:20:03 -04:00
298483131b
providers/aws: fixed tons of aws stuff
2014-07-24 18:50:33 -04:00
Panagiotis Moustafellos