📢 This module is no longer maintained. We recommend using a newer version from terraform-do-modules for better performance and stability. If you have any questions or concerns, please don't hesitate to ask for assistance.
spaces are virtual networks containing resources that can communicate with each other in full isolation, using private IP addresses.
We eat, drink, sleep and most importantly love DevOps. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy Bigger problems are always solved by breaking them into smaller manageable problems. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller connected yet manageable pieces within the infrastructure.
This module is basically combination of Terraform open source and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
We have fifty plus terraform modules. A few of them are comepleted and are available for open source usage while a few others are in progress.
This module has a few dependencies:
- Terraform 0.15
- Go
- github.com/stretchr/testify/assert
- github.com/gruntwork-io/terratest/modules/terraform
IMPORTANT: Since the master
branch used in source
varies based on new modifications, we suggest that you use the release versions here.
Here is an example of how you can use this module in your inventory structure:
module "spaces" {
source = "terraform-do-modules/spaces/digitalocean"
version = "0.15.0"
name = "clouddrove"
environment = "test"
label_order = ["name"]
acl = "public-read"
force_destroy = true
region = "nyc3"
}
Name | Description | Type | Default | Required |
---|---|---|---|---|
abort_incomplete_multipart_upload_days | Specifies the number of days after initiating a multipart upload when the multipart upload must be completed or else Spaces will abort the upload. | number |
null |
no |
acl | Canned ACL applied on bucket creation (private or public-read). | string |
null |
no |
attributes | Additional attributes (e.g. 1 ). |
list(any) |
[] |
no |
cors_rule | CORS Configuration specification for this bucket | list(object({ |
null |
no |
date | pecifies the date/time after which you want applicable objects to expire. The argument uses RFC3339 format, e.g.(2020-03-22T15:03:55Z) or parts thereof e.g. 2019-02-28. | string |
null |
no |
delimiter | Delimiter to be used between organization , environment , name and attributes . |
string |
"-" |
no |
environment | Environment (e.g. prod , dev , staging ). |
string |
"" |
no |
expiration_days | Specifies the number of days after object creation when the applicable objects will expire. | number |
null |
no |
expired_object_delete_marker | On a versioned bucket (versioning-enabled or versioning-suspended bucket), setting this to true directs Spaces to delete expired object delete markers. | string |
"" |
no |
force_destroy | Unless true, the bucket will only be destroyed if empty (Defaults to false). | bool |
false |
no |
label_order | Label order, e.g. name ,application . |
list(any) |
[] |
no |
name | Name (e.g. app or cluster ). |
string |
"" |
no |
noncurrent_version_expiration | On a versioned bucket (versioning-enabled or versioning-suspended bucket), setting this to true directs Spaces to delete expired object delete markers. | string |
"" |
no |
prefix | (Optional, Forces new resource) Creates a unique bucket name beginning with the specified prefix. | string |
null |
no |
region | The region to create VPC, like london-1 , bangalore-1 ,newyork-3 toronto-1 . |
string |
"" |
no |
versioning | (Optional) A state of versioning (documented below). | bool |
true |
no |
Name | Description |
---|---|
bucket_domain_name | The date and time of when the VPC was created. |
name | The date and time of when the VPC was created. |
urn | The uniform resource name (URN) for the VPC. |
In this module testing is performed with terratest and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a GO environment in your system.
You need to run the following command in the testing folder:
go test -run Test
If you come accross a bug or have any feedback, please log it in our issue tracker, or feel free to drop us an email at hello@clouddrove.com.
If you have found it worth your time, go ahead and give us a ★ on our GitHub!
At CloudDrove, we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
We are The Cloud Experts!
We ❤️ Open Source and you can check out our other modules to get help with your new Cloud ideas.