fa8cb0f495
link new openstack resource docs into sidebar
2015-05-08 18:14:02 +02:00
8dd1f939e2
Merge pull request #1864 from TimeIncOSS/fix-docs-links
...
Fix docs 404, typos and incorrect references
2015-05-08 10:01:30 -05:00
73651e2c70
providers/aws: Extract normalizeRegion
2015-05-08 10:49:21 -04:00
445f92e48a
providers/aws: Move HostedZoneIDForRegion into TF
2015-05-08 10:49:20 -04:00
64d2b495c3
providers/aws: Add region to S3 attrs
2015-05-08 10:02:16 -04:00
839688d477
providers/aws: Add hosted_zone_id to S3 attrs
2015-05-08 10:02:16 -04:00
d7c9d8702c
providers/aws: Extract website endpoint logic
2015-05-08 10:02:16 -04:00
4a99cf9e9f
Small update/fix to properly clean ANSI going to the logfile...
2015-05-08 14:54:56 +02:00
60984b2da2
This commit adds a Chef Client provisioner
...
The commit is pretty complete and has a tested/working provisioner for
both SSH and WinRM. There are a few tests, but we maybe need another
few to have better coverage. Docs are also included…
2015-05-08 14:54:56 +02:00
be2ab3a644
Duplicate of vpn-gateway link removed
2015-05-08 10:40:56 +01:00
c6a9a0684a
Incorrect references fixed
2015-05-08 10:40:56 +01:00
ff1e4427cd
Typo fixed (vpc -> vpn)
2015-05-08 10:40:56 +01:00
dfae8e1170
Do matching in sidebar_current via regex or equal sign
2015-05-08 10:40:51 +01:00
f1ae920aa9
website: document templating as a provider
2015-05-07 18:20:22 -07:00
c9e0ada075
Update CHANGELOG.md
2015-05-07 18:31:22 -05:00
c9af8c615b
deps for v0.5.0
...
full Godeps `_workspace` captured on deps/v0.5.0 branch
2015-05-07 18:00:56 -05:00
0c48db6c45
up version for dev
2015-05-07 15:56:16 -07:00
33e11f0eba
v0.5.0
2015-05-07 15:26:49 -07:00
b487c65cfb
Merge pull request #1860 from hashicorp/cts-changelog
...
update changelog
2015-05-07 17:26:26 -05:00
e6f5970c67
update changelog
2015-05-07 17:25:12 -05:00
60c3ca0430
typo
2015-05-07 23:21:47 +01:00
44461f49fd
update structure test
2015-05-07 17:18:47 -05:00
70984526a4
Merge remote-tracking branch 'ctiwald/ct/fix-protocol-problem'
...
* ctiwald/ct/fix-protocol-problem:
aws: Document the odd protocol = "-1" behavior in security groups.
aws: Fixup structure_test to handle new expandIPPerms behavior.
aws: Add security group acceptance tests for protocol -1 fixes.
aws: error on expndIPPerms(...) if our ports and protocol conflict.
2015-05-07 17:13:21 -05:00
4874179e9a
Merge pull request #1843 from ctiwald/ct/fix-network-acls
...
Fix a number of issues in AWS network ACLs
2015-05-07 16:39:10 -05:00
fc084cc03e
Merge pull request #1857 from hashicorp/b-multi-mod
...
terraform: flattening multi-level modules works
2015-05-07 13:34:35 -07:00
750b8c7fd5
Merge pull request #1855 from hashicorp/b-module-cycle
...
Only depend on variables for counts for destroy nodes
2015-05-07 13:28:09 -07:00
6d56a2ac86
terraform: comment
2015-05-07 13:10:25 -07:00
7c3e355bb0
terraform: flattening multi-level modules works
2015-05-07 13:08:59 -07:00
caef7769ae
dag: Replace with the same values is a no-op
2015-05-07 11:22:07 -07:00
6752ccfe10
terraform: only include variables in graph if count of a resource
...
depends
2015-05-07 10:50:56 -07:00
e8d19637d3
provider/terraform: test fixture
2015-05-07 09:59:23 -07:00
ddad945717
provider/terraform: test fixture
2015-05-07 09:59:23 -07:00
6586ce243c
update gitignore so the acceptance test for terraform gets in
2015-05-07 09:59:23 -07:00
bc9792f4c5
helper/schema: tweak test anotation
2015-05-07 10:39:17 -05:00
051ba78554
Merge pull request #1824 from hashicorp/b-write-count-for-empty-maps
...
helper/schema: write "attr.#": "0" for empty maps
2015-05-07 10:38:32 -05:00
1594cb3dbe
provider/aws: remove names from LCs in ASG tests
...
Makes the tests a little more durable if your account happens to end up
with a dangling LC.
2015-05-07 10:14:49 -05:00
20ebb38b8f
update s3bucket website tests
2015-05-07 10:13:08 -05:00
ef62385a95
Merge pull request #1849 from hashicorp/f-aws-update-s3-website-tests
...
update tests so go vet is happy
2015-05-07 10:06:43 -05:00
fed42fe1b3
update tests so go vet is happy
2015-05-07 10:03:28 -05:00
44e448b8c9
provider/docker: update image sha
...
Should eventually see if there's a way to rework this so it's less
brittle. But for now, we band-aid!
2015-05-07 09:50:16 -05:00
28875f49cd
provider/heroku: fix config_vars in addons
...
These were never read properly - on Addons they show up as just a list
of var names, not a Map.
Fixes one issue in Addon acceptance tests.
2015-05-07 09:11:31 -05:00
e7b101dba4
provider/aws: elasticache_cluster engine_version is computed
...
fixes the TestAccAWSElasticacheCluster test
2015-05-07 08:47:52 -05:00
f1c8b555ab
Update CHANGELOG.md
...
#1778
2015-05-07 08:34:39 -05:00
0688431715
aws: Document network ACL's new validations.
2015-05-07 00:02:48 -04:00
6b2e0b938d
terraform: only omit vars on full destroys
2015-05-06 20:55:14 -07:00
9e8aefcd40
aws: Fix network ACL acceptance tests and add -1 protocol rule.
2015-05-06 23:54:14 -04:00
5b0d61727e
aws: Only store protocol numbers for ingress/egress rules on ACLs.
...
Users can input a limited number of protocol names (e.g. "tcp") as
inputs to network ACL rules, but the API only supports valid protocol
number:
http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
Preserve the convenience of protocol names and simultaneously support
numbers by only writing numbers to the state file. Also use numbers
when hashing the rules, to keep everything consistent.
2015-05-06 23:54:12 -04:00
8056b5f8f7
aws: Force users to use valid network masks on ACL ingress/egress
...
AWS will accept any overly-specific IP/mask combination, such as
10.1.2.2/24, but will store it by its implied network: 10.1.2.0/24.
This results in hashing errors, because the remote API will return
hashing results out of sync with the local configuration file.
Enforce a stricter API rule than AWS. Force users to use valid masks,
and run a quick calculation on their input to discover their intent.
2015-05-06 23:53:34 -04:00
b888b31e08
aws: Force users to use from_port, to_port = 0 on network ACLs with -1 protocol
...
AWS doesn't store ports for -1 protocol rules, thus the read from the
API will always come up with a different hash. Force the user to make a
deliberate port choice when enabling -1 protocol rules. All from_port
and to_port's on these rules must be 0.
2015-05-06 23:51:23 -04:00
19b33326be
terraform: don't include variables in destroy node requirements
2015-05-06 20:13:19 -07:00
Alexander Dupuy