This repository has been archived by the owner on Jan 30, 2021. It is now read-only.
Releases: cloudposse-archives/terraform-aws-kops-state-backend
Releases · cloudposse-archives/terraform-aws-kops-state-backend
0.3.0: Allow use of existing S3 bucket in other region
0.2.0 Add flag to disable public access in `kops` state bucket by default
what
- Add flag to disable public access in
kops
state bucket by default
why
- Security by design
0.1.8
0.1.7: Update terraform-aws-route53-cluster-zone to 0.3.1
0.1.6: Update readme yaml file and rebuild md
what
- updated
README.yaml
file - add tags and categories
- rebuild
README.md
file
why
- need to add categories and tags so we can pull them into the documentation
0.1.5
Migrate to README.yaml format
what
- Add
README.yaml
why
- Standardize README
0.1.3
0.1.2
what
- Separate S3 bucket name from Kops cluster name
why
-
Almost always we want to use the bucket name like this
cp-prod-kops-state
withkops
in the name to correctly represent the technology (kops
in this case) the bucket is used to store the state for -
But for the
kops
cluster names, we want to use a role-based naming convention instead of technology-based, e.g.cluster-1.prod.domain.com
or location-based naming convention likeus-west-2.prod.domain.com
0.1.1
what
- Rename repo
- Update module
- Update
README
with examples - Add TravisCI
why
- Use
terraform-aws-kops-*
naming convention forkops
modules - Use common conventions for naming resources
- Cloud Posse
README
template - For
terraform lint
and monitoring build status
test
{
"ResourceTagSets": [
{
"ResourceType": "hostedzone",
"ResourceId": "Z58RWQWFVU4HT",
"Tags": [
{
"Key": "Cluster",
"Value": "kops.cloudxl.net"
},
{
"Key": "Stage",
"Value": "prod"
},
{
"Key": "Namespace",
"Value": "cp"
},
{
"Key": "Name",
"Value": "cp-prod-kops-state"
}
]
}
]
}