Spinless will be in charge of managing infrastructure resources.
Any infrastructure should be created by spinless using terraform
Resource would be represented by :
name
type
properties
Any resource type would be mapped to terraform infrastructure (kept in github - link to github _ version)
Resource's state would be kept in S3 bucket.
terraform state in S3 will have the following naming:
$bucket/$resource_type/$resource_name/
where:
bucket = exberry-terraform-states-$account ( for example exberry-terraform-states-staging)
resource_type - type of resource (for example 'cloud'/'kafka'/postgress'/...)
resource_name - name (identifier)of resource - for example, 'kafka-ldx-stg', 'shared-kafka-testing', 'kafka-ldx-prod45'
Spinless should manage mapping between resource type and terraform sources:
Spinless will be in charge of managing infrastructure resources.
Any infrastructure should be created by spinless using terraform
Resource would be represented by :
Any resource type would be mapped to terraform infrastructure (kept in github - link to github _ version)
Resource's state would be kept in S3 bucket. terraform state in S3 will have the following naming:
where:
Spinless should manage mapping between resource type and terraform sources:
Requests to create resources with the same type and name should be idempotent
Sample request (create resource): POST https://spinless.stg.com/resources
Sample request (delete resources) DELETE https://spinless.stg.com/resources/${resource_type}/${resource_name}