564b7e1e67
providers/aws: Add docs for S3 website
2015-05-06 08:15:56 -04:00
348942d3fb
providers/aws: Use GetOk instead of Get + cast
2015-05-06 08:15:56 -04:00
562bd6541b
providers/aws: Use explicit returns in websiteEndpoint
2015-05-06 08:15:56 -04:00
30f737c781
providers/aws: Change S3 website to block
2015-05-06 08:15:56 -04:00
38e04b3765
providers/aws: Add website_endpoint to S3 output
2015-05-06 08:15:55 -04:00
b7a9ef5ef6
providers/aws: Add S3 error_document
...
Also fix when index/error document is empty
2015-05-06 08:15:55 -04:00
e6d9dcfb1a
providers/aws: Initial S3 bucket website support
2015-05-06 08:15:55 -04:00
cebcee5c63
Merge pull request #1778 from josharian/template-provider
...
providers: add template provider
2015-05-05 20:09:27 -05:00
1a2bac7645
provider/aws: main route table refresh handles VPC being gone [GH-1806]
2015-05-05 18:07:22 -07:00
b085342274
Merge pull request #1816 from hashicorp/b-validate-plan-graph-not-verbose-graph
...
core: validate graph w/ diff during plan phase
2015-05-05 19:57:59 -05:00
56e92f7f02
website: document state
2015-05-05 17:52:28 -07:00
0fff7d1673
core: validate graph w/ diff during plan phase
...
This reimplements my prior attempt at nipping issues where a plan did
not yield the same cycle an apply did. My prior attempt was to have
ctx.Validate generate a "Verbose" worst-case graph. It turns out that
skipping PruneDestroyTransformer to generate this graph misses important
heuristics that prevent cycles by dropping destroy nodes that are
determined to be unused.
This resulted in Validate improperly failing in scenarios where these
heuristics would have broken the cycle.
We detected the problem during the work on #1781 and worked around the
issue by reverting to the non-Verbose graph in Validate.
This commit accomplishes the original goal in a better way - by
generating the full graph and checking it once Plan has calculated the
diff. This guarantees that any graph issue that would be caught by Apply
will be caught by Plan.
2015-05-05 17:24:44 -05:00
df7603520b
Update CHANGELOG.md
...
provider/aws: Add Security Group Rule as a top level resource #1620
2015-05-05 17:13:44 -05:00
9510c716aa
Merge pull request #1620 from hashicorp/f-aws-security-group-rule-resource
...
provider/aws: Add Security Group Rule as a top level resource
2015-05-05 17:12:15 -05:00
885efa0837
provider/aws: Add Security Group Rule as a top level resource
...
- document conflict with sg rules and sg in-line rules
- for this to work, ingress rules need to be computed
2015-05-05 16:56:39 -05:00
96e91c1cbd
Update CHANGELOG.md
2015-05-05 16:48:48 -05:00
a4000941c2
Merge pull request #1765 from hashicorp/f-aws-security-group-remove-default-egress
...
provider/aws: Remove default egress rule from Security Group on creation
2015-05-05 16:47:23 -05:00
febc8643af
website: add prpogating_vgws
2015-05-05 14:44:07 -07:00
9161454e78
update CHANGELOG
2015-05-05 14:43:23 -07:00
fb4ac42c65
Merge pull request #1516 from henrikhodne/aws-propagating-vgws
...
provider/aws: add propagating_vgws to route tables
2015-05-05 14:42:45 -07:00
eb7c1bb218
fix go formatting
2015-05-05 16:42:08 -05:00
e9b08cf31f
revert the required part
2015-05-05 16:23:26 -05:00
1ed81da9a9
update ENI test for SG egress constraint
2015-05-05 16:23:26 -05:00
85b1756c27
revise tests and check for vpc_id
2015-05-05 16:23:26 -05:00
8ded3c2d1b
Move block for deleing default rule into the create method; only invoke once
2015-05-05 16:23:26 -05:00
ee65684abe
Add spec for removing default egress rule
2015-05-05 16:23:26 -05:00
b145ce88b7
Document Egress+VPC change, update link
2015-05-05 16:23:26 -05:00
1558fd1c3e
provider/aws: Remove default egress rule from Security Group on creation
2015-05-05 16:23:25 -05:00
27a616ade1
update cHANGELOG
2015-05-05 13:30:57 -07:00
b40c87391b
update cHANGELOG
2015-05-05 13:29:22 -07:00
412a2dca0b
Merge pull request #1575 from freshbooks/aws-eni-route
...
provider/aws: Add Elastic Network Interfaces as route destination
2015-05-05 13:28:48 -07:00
d582d0eb13
update CHANGELOG
2015-05-05 13:26:29 -07:00
379895931d
website: network interface for EIP
2015-05-05 13:25:45 -07:00
7a22376742
Merge branch 'jstremick-f-aws-associate-eip-to-eni'
2015-05-05 13:24:58 -07:00
1c2d5fbd0a
Merge branch 'f-aws-associate-eip-to-eni' of https://github.com/jstremick/terraform into jstremick-f-aws-associate-eip-to-eni
2015-05-05 13:24:50 -07:00
c8635654cb
Merge pull request #1781 from hashicorp/b-module-deps
...
Flatten modules into main graph
2015-05-05 13:19:41 -07:00
ad539d3c96
Update CHANGELOG.md
2015-05-05 15:10:34 -05:00
a07f07bbf2
Merge pull request #1813 from svanharmelen/b-aws-creds-fix
...
Fixing PR #1804
2015-05-05 13:05:35 -07:00
0f40cebc0f
Merge pull request #1814 from svanharmelen/b-fix-small-vet-warning
...
Fixing a small vet warning introduced by PR #1796
2015-05-05 13:05:11 -07:00
18b43b78cb
Merge pull request #939 from bitglue/iam
...
Implement a subset of IAM resources
2015-05-05 15:05:05 -05:00
8c34e9a36a
terraform: provisionedby prefixed
2015-05-05 13:04:27 -07:00
7b082d007e
Merge commit '33183c0'
...
* commit '33183c0':
Implement a hash function for string sets
2015-05-05 15:01:02 -05:00
3881c81a66
Added the exit code as well...
2015-05-05 21:56:20 +02:00
d503cc2d82
terraform: flattenable graphNodeMissingProvisioner
2015-05-05 12:45:28 -07:00
48f4d499f9
Fixing a small vet warning introduced by PR #1796
...
While fixing the vet warning also tried to improve any feedback by
showing the actual output/error instead of just the error code.
While testing this I noticed only adding stderr output is not enough as
not all error info is send to stderr, but sometimes also to stdout.
2015-05-05 21:26:28 +02:00
6d4969f64c
terraform: run prune destroy on validate
2015-05-05 12:11:49 -07:00
897bf5e53d
Added `SharedCredentialsProvider` and `EC2RoleProvider` as well...
2015-05-05 20:38:35 +02:00
5435815524
Fixing PR #1804
2015-05-05 20:30:35 +02:00
1045fb9eac
Merge pull request #1811 from hashicorp/b-aws-auth
...
providers/aws: chain credentials
2015-05-05 10:55:40 -07:00
803348d05f
Merge pull request #1797 from hashicorp/b-flatten-modules-cycle
...
core: failing test for a bad module cycle
2015-05-05 10:54:57 -07:00
Justin Campbell