Commit Graph

12 Commits

Author SHA1 Message Date
Sander van Harmelen c14aa6336e Delete all deprecated parameters before the 0.7 release
Updated the docs accordingly and also executed all the acceptance tests
after making the changes…
2016-06-27 11:13:48 +02:00
Sander van Harmelen 815c8840a7 Refactor the use of names vs IDs for parameters referencing other TF resources
We have a curtesy function in place allowing you to specify both a
`name` of `ID`. But in order for the graph to be build correctly when
you recreate or taint stuff that other resources depend on, we need to
reference the `ID` and *not* the `name`.

So in order to enforce this and by that help people to not make this
mistake unknowingly, I deprecated all the parameters this allies to and
changed the logic, docs and tests accordingly.
2016-04-11 17:14:28 +02:00
Sander van Harmelen fddf3eccc6 Make the CloudStack provider more inline with the other provider
It turns out all other providers use `ip_address` where the CloudStack
provider uses `ipaddress`. To make this more consistent this PR
deprecates `ipaddress` and adds `ip_address` where needed…
2016-04-04 22:16:15 +02:00
Sander van Harmelen 3385100f56 Make the concurrence for applying rules configurable 2016-01-21 21:30:54 +01:00
Sander van Harmelen b8f3417e79 Change all firewall related resources to take a cidr_list
Also some additional tweaks to improve performance and add in a little
concurrency to speed things up a little.
2015-12-03 15:34:53 +01:00
Sander van Harmelen 28b7b53be6 Updates and tweaks 2015-07-16 17:40:11 +02:00
Sander van Harmelen bb7ef8db67 Adding tests and docs for the new VPN resources
And did some (very) minor refactoring in the existing docs
2015-03-09 14:00:29 +01:00
Sander van Harmelen edc8b91d09 Adding/updating the docs to reflect the changes in the provider 2015-01-16 17:23:27 +01:00
Mitchell Hashimoto 577e2420b0 Revert "docs: consistent use of array configuration syntax"
This reverts commit 4893eb8b55.
2015-01-14 09:28:25 -08:00
Emil Hessman 4893eb8b55 docs: consistent use of array configuration syntax
The Terraform configuration syntax defines what arrays are.
Use the word array consistently throughout the documentation
instead of list.

The corresponding JSON datatype is called array as well, and
since the Terraform configuration syntax is interoperable with
JSON it makes sense to use the term array to describe them.
2015-01-13 06:59:12 +01:00
Emil Hessman 28d39cd0bc website: address spelling mistakes, casing and links 2015-01-03 19:31:53 +01:00
Sander van Harmelen 4910423d83 First release of a provider for CloudStack
Of course not all resources are covered by this first release, but
there should be enough resources available to handle most common
operations.

Tests and docs are included.
2014-12-10 22:20:52 +01:00