198e1a5186
remove various typos
2015-09-11 11:56:20 -07:00
0c2f189d08
provider/aws: Update to aws-sdk 0.9.0 rc1
2015-08-17 13:27:16 -05:00
579ccbefea
provider/aws: Update source to comply with upstream breaking change
2015-07-28 15:29:46 -05:00
7756bf3aef
provider/aws: Fix issue with detecting differences in DB Parameters
...
Fixes #2718
2015-07-14 14:47:18 -05:00
cc79e6cb8d
provider/aws: Fix issue in Classic env with external Security Groups
...
Linking a security group from another account requires setting the UserID, which
we were stripping out
2015-07-07 12:06:36 -06:00
a6010e6317
frist commit for aws_elasticahce_parameter_group
2015-06-08 21:05:00 +02:00
ebaa9bde2a
provider/aws: Add new resource - aws_ecs_service
2015-06-03 22:48:17 +01:00
87faf855aa
provider/aws: Add new resource - aws_ecs_task_definition
2015-06-03 22:47:32 +01:00
b71fa3d0ae
provider/aws: handle upstream aws-sdk-go repo move
...
`awslabs/aws-sdk-go => aws/aws-sdk-go`
Congrats to upstream on the promotion. :)
2015-06-03 13:36:57 -05:00
89bacc0b15
aws: error on expndIPPerms(...) if our ports and protocol conflict.
...
Ingress and egress rules given a "-1" protocol don't have ports when
Read out of AWS. This results in hashing problems, as a local
config file might contain port declarations AWS can't ever return.
Rather than making ports optional fields, which carries with it a huge
headache trying to distinguish between zero-value attributes (e.g.
'to_port = 0') and attributes that are simply omitted, simply force the
user to opt-in when using the "-1" protocol. If they choose to use it,
they must now specify "0" for both to_port and from_port. Any other
configuration will error.
2015-05-04 23:43:31 -04:00
5c1dabdb69
provider/aws: Add ProxyProtocol support via aws_proxy_protocol_policy
2015-04-30 17:56:46 +09:00
0c5011bea4
provider/aws: Fix issue with empty IPRanges
2015-04-21 10:57:50 -05:00
3e6822ce08
more cleans ups of SDK reference
2015-04-16 15:28:18 -05:00
79fc8223bb
consolidate structure.go
2015-04-16 15:18:01 -05:00
1545dbb803
provider/aws: Convert Route 53 Zone, Record to upstream
2015-04-16 13:41:38 -05:00
29a5d9fc1a
Update how we expand/flatten TXT records for Route 53
2015-04-08 13:58:23 -05:00
f2b68c4ca8
provider/aws: Fix issue in updating Route 53 records on refresh/read.
...
Route 53 records were silently erroring out when saving the records returned
from AWS, because they weren't being presented as an array of strings like we
expected.
2015-04-08 09:06:15 -05:00
df514c9003
Merge pull request #1149 from peterbeams/master
...
Support AWS Elastic Network Interfaces (ENI)
2015-03-19 11:04:30 -05:00
d823a8cf81
providers/aws: fix security group self ingress rules on EC2-classic
2015-03-18 13:47:59 +00:00
e4214a9983
ran go fmt and made 1 fix after running tests again
2015-03-17 13:00:36 +00:00
34d2efa7df
moving expand/flatten methods into structure.go and unit testing them
2015-03-17 12:42:05 +00:00
28fbd971fc
Retire goamz
2015-03-13 09:42:50 -05:00
580b696e7f
Strike 'goamz' from the repo'
2015-03-12 16:49:38 -05:00
3977256c17
Cleansup: Restore expandIPPerms, remove flattenIPPerms
2015-03-10 16:35:49 -05:00
20b02cacd4
provider/aws: Convert AWS Security Group to aws-sdk-go
...
Convert security group test too
2015-03-09 11:45:58 -05:00
da55f9bf85
provider/aws: Convert AWS ELB to aws-sdk-go
2015-03-02 09:44:06 -06:00
242cdc7a29
provider/aws: Convert RDS DB Parameter group to aws-sdk-go
2015-02-26 09:33:33 -06:00
8eb5418c4a
Implement apply_method for RDS parameters
...
This is necessary to support creating parameter groups with parameters
that require a reboot, since the RDS API will return an error when
attempting to set those parameters with ApplyMethod "immediate".
2015-01-30 13:06:15 -05: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
d3e1a6678d
Making some last tweaks and fixing some acc tests
2014-11-24 21:22:18 +01:00
a14da63a39
Fixed bug with final_snapshot_identifier and skip_final_snapshot and removed apply_method as an option for now and am only supporting immediate mode
2014-11-05 11:03:06 -08:00
0e3afa6d3d
Fixed incorrect ForcesNew settings for parameters and added better acceptance tests to ensure updates are working as expected
2014-11-05 11:03:06 -08:00
3b54001a1b
Added missing update support for new aws_db_parameter_group resource
2014-11-05 11:03:06 -08:00
de16b10555
Added new aws_db_parameter_group resource for creating RDS DB Parameter Groups.
...
Added plumbing to allow an optional DBParameterGroupName to be passed when creating an RDS DB instance.
2014-11-05 11:03:06 -08:00
f63a5d24e9
helper/schema: diffs for sets should include the full set [GH-457]
...
Prior to this, the diff only contained changed set elements. The issue
with this is that `getSet`, the internal function that reads a set from
the ResourceData, expects that each level (state, config, diff, etc.)
has the _full set_ information. This change was done to fix merging
issues.
Because of this, we need to make sure the full set is visible in the
diff.
2014-10-21 10:49:53 -07:00
152d5b0c69
providers/aws: elb properly hashes listeners
2014-10-16 18:02:03 -07:00
1a2afdaa37
providers/aws: launch config and autoscale group load is correct
...
[GH-423]
2014-10-16 16:39:58 -07:00
51d66b678d
providers/aws: resource ELB listeners [GH-314]
2014-10-10 16:35:52 -07:00
12ff354749
providers/aws: convert most of ELB to schema
2014-10-09 23:58:48 -07:00
3aa655ad3b
helper/schema: test schema diffs with the interpolation splits
2014-10-09 16:31:24 -07:00
d01418270a
Add listener.ssl_certificate_id support to AWS ELB (@jpadvo [GH-176])
2014-10-02 05:19:36 +03:00
dbc890e401
providers/aws: add `self` to ingress [GH-219]
2014-09-30 14:19:16 -07:00
a594ef9a28
providers/aws: expandIPPerms works again
2014-08-20 11:18:16 -07:00
8d97c3656c
Add listener.ssl_certificate_id support to AWS ELB
2014-08-10 17:16:53 -07:00
7109b8c770
Implement specification of AWS security groups in ingress rules as <owner>/<id>
2014-08-08 11:51:18 -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
4f2026f6c6
providers/aws: only flatten cidr if they exist
...
fixes #87
2014-07-29 10:29:48 -04:00
da4ddef136
providers/aws: fix assertion of non-required cidr blocks in sec groups
...
fixes #65 , #86
2014-07-29 10:05:32 -04:00
298483131b
providers/aws: fixed tons of aws stuff
2014-07-24 18:50:33 -04:00
Anthony Scalisi