c250c10d4e
Force the master username & password to be defined when not in a restore mode
2016-12-04 19:04:26 +01:00
5481e9ecb3
provider/aws: Enforced kms_key_* attributes to be ARNs ( #10356 )
...
* Added kms_key_* validation to force ARNs
* Added Redshift Cluster KMS key test
* Added cloudtrail kms key test
* Added EBS volume kms key
* Added Elastic Transcoder Pipeline kms key arn test
2016-11-30 13:50:26 +02:00
e9821eaced
Updated Redshift Documentation and Added Test Cases for Redshift Enchaned VPC routing
2016-11-08 18:13:10 +05:30
d96a439029
Added missing argument for redshift cluster ( #9831 )
2016-11-03 14:47:19 +00:00
50eb2338f0
Correct a typo in the description of the master_password argument. ( #9004 )
2016-09-22 15:58:02 -05:00
01fca172cb
provider/aws: Removing the merge conflict from the redshift_cluster resource
2016-08-24 20:50:06 +01:00
3a2d73a2b1
provider/aws: Add support to `aws_redshift_cluster` for restoring from ( #8414 )
...
snapshot
Fixes #6406
Adds 2 new parameters:
* `snapshot_identifier`
* `snapshot_cluster_identifier`
These will be used to allow the Redshift cluster to be restored from a
pre-existing snapshot. Also makes the redshift username and password
fields optional as these are not required for the snapshot
```
% make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSRedshiftCluster_'
==> Checking that code complies with gofmt requirements...
/Users/stacko/Code/go/bin/stringer
go generate $(go list ./... | grep -v /terraform/vendor/)
2016/08/23 12:04:53 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v
-run=TestAccAWSRedshiftCluster_ -timeout 120m
=== RUN TestAccAWSRedshiftCluster_importBasic
--- PASS: TestAccAWSRedshiftCluster_importBasic (741.03s)
=== RUN TestAccAWSRedshiftCluster_basic
--- PASS: TestAccAWSRedshiftCluster_basic (656.33s)
=== RUN TestAccAWSRedshiftCluster_loggingEnabled
--- PASS: TestAccAWSRedshiftCluster_loggingEnabled (718.65s)
=== RUN TestAccAWSRedshiftCluster_iamRoles
--- PASS: TestAccAWSRedshiftCluster_iamRoles (818.10s)
=== RUN TestAccAWSRedshiftCluster_publiclyAccessible
--- PASS: TestAccAWSRedshiftCluster_publiclyAccessible (853.30s)
=== RUN TestAccAWSRedshiftCluster_updateNodeCount
--- PASS: TestAccAWSRedshiftCluster_updateNodeCount (2083.37s)
=== RUN TestAccAWSRedshiftCluster_tags
--- PASS: TestAccAWSRedshiftCluster_tags (621.15s)
PASS
ok github.com/hashicorp/terraform/builtin/providers/aws
6491.963s
```
When deploying this, I was able to use config as follows:
```
resource "aws_redshift_cluster" "restore" {
cluster_identifier = "my-test-restored-cluster"
snapshot_identifier = "sample-snapshot-for-restore"
node_type = "dc1.large"
}
```
And it resulted in:
```
terraform apply
[WARN] /Users/stacko/Code/go/bin/terraform-provider-aws overrides an internal plugin for aws-provider.
If you did not expect to see this message you will need to remove the old plugin.
See https://www.terraform.io/docs/internals/internal-plugins.html
aws_redshift_cluster.restore: Creating...
allow_version_upgrade: "" => "true"
automated_snapshot_retention_period: "" => "1"
availability_zone: "" => "<computed>"
bucket_name: "" => "<computed>"
cluster_identifier: "" => "my-test-restored-cluster"
cluster_parameter_group_name: "" => "<computed>"
cluster_public_key: "" => "<computed>"
cluster_revision_number: "" => "<computed>"
cluster_security_groups.#: "" => "<computed>"
cluster_subnet_group_name: "" => "<computed>"
cluster_type: "" => "<computed>"
cluster_version: "" => "1.0"
database_name: "" => "<computed>"
enable_logging: "" => "false"
encrypted: "" => "<computed>"
endpoint: "" => "<computed>"
iam_roles.#: "" => "<computed>"
kms_key_id: "" => "<computed>"
node_type: "" => "dc1.large"
number_of_nodes: "" => "1"
port: "" => "5439"
preferred_maintenance_window: "" => "<computed>"
publicly_accessible: "" => "true"
s3_key_prefix: "" => "<computed>"
skip_final_snapshot: "" => "true"
snapshot_identifier: "" => "sample-snapshot-for-restore"
vpc_security_group_ids.#: "" => "<computed>"
..........
aws_redshift_cluster.restore: Still creating... (5m20s elapsed)
aws_redshift_cluster.restore: Creation complete
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
```
2016-08-24 10:58:05 +01:00
2195a67748
Ensure kms_key_id docs indicate it is an ARN ( #7842 )
...
If you specify just a bare ID, then the initial application works but
subsequent applications may end up doing bad things, like:
```
-/+ aws_ebs_volume.vol_1
availability_zone: "us-east-1a" => "us-east-1a"
encrypted: "true" => "true"
iops: "" => "<computed>"
kms_key_id: "arn:aws:kms:us-east-1:123456789:key/59faf88b-0912-4cca-8b6c-bd107a6ba8c4" => "59faf88b-0912-4cca-8b6c-bd107a6ba8c4" (forces new resource)
size: "100" => "100"
snapshot_id: "" => "<computed>"
```
2016-07-28 08:44:09 +01:00
3f83f0b9f9
provider/aws: Enable Redshift Cluster Logging ( #7813 )
...
Fixes #7423
```
% make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSRedshiftCluster_loggingEnabled'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /terraform/vendor/)
TF_ACC=1 go test ./builtin/providers/aws -v
-run=TestAccAWSRedshiftCluster_loggingEnabled -timeout 120m
=== RUN TestAccAWSRedshiftCluster_loggingEnabled
--- PASS: TestAccAWSRedshiftCluster_loggingEnabled (675.21s)
PASS
ok github.com/hashicorp/terraform/builtin/providers/aws 675.233s
```
2016-07-27 22:16:32 +01:00
5f6ea8b18e
documentation/aws: More additions of Import documention to the AWS ( #7729 )
...
resources
2016-07-20 23:28:59 +01:00
ce4841e6a6
provider/aws: Add support to `aws_redshift_cluster` for ``iam_roles`` ( #6647 )
2016-05-24 22:44:46 +01:00
1df8290134
provider/aws: Support tags for AWS redshift cluster ( #5356 )
2016-05-24 18:43:12 +01:00
faa6ddb2ee
provider/aws: Support for Redshift Cluster encryption using a KMS key ( #6712 )
2016-05-17 11:12:39 -05:00
dc30bd29fc
provider/aws: Redshift Cluster not allowing 0 for ( #6537 )
...
automated_snapshot_retention_period
The default value for `automated_snapshot_retention_period` is 1.
Therefore, it can be included in the `CreateClusterInput` without
needing to check that it is set.
This was actually stopping people from setting the value to 0 (disabling
the snapshots) as there is an issue in `d.GetOk()` evaluating 0 for int
2016-05-08 19:29:36 +01:00
e822d46843
provider/aws: `aws_redshift_cluster` publicly_accessible now defaults to
...
true
2016-02-22 23:11:55 +00:00
e6e18a4a9e
provider/aws: Change Redshift Cluster cluster_type to be computed
...
It will be based off the number of nodes. Can only be multi-node (>1
node) or single-node (nodes=1)
2016-02-21 19:42:02 +00:00
9407f538cf
Changing the default for ship_final_snapshot on redshift_cluster to be true so as to match the code
2016-01-31 21:48:05 +00:00
8181a4ea24
minor clean ups after #3862
2016-01-13 16:58:07 -06:00
bf03752552
Adding the documentation for the AWS Redshift Subnet Group resource
...
also removed the notion of tags from the redshift security group and
parameter group documentation until that has been implemented
Redshift Cluster CRUD and acceptance tests
Removing the Acceptance test for the Cluster Updates. You cannot delete
a cluster immediately after performing an operation on it. We would need
to add a lot of retry logic to the system to get this test to work
Adding some schema validation for RedShift cluster
Adding the last of the pieces of a first draft of the Redshift work - this is the documentation
2015-12-20 20:20:05 +00:00
Ninir