Record v0.14, the release that spent nothing - #57
Merged
Conversation
Fifteen pull requests since v0.13, with one theme: settle everything
about a cloud apply that can be settled without performing one.
Five real defects, none of which the twenty-seven checks could see:
- the node security group admitted the load balancer, but instance
targets preserve the client address, so it matched health checks and
nothing else -- healthy targets, no reachable cluster
- snapshot uploads had no kms:GenerateDataKey, so every hourly upload
would have been denied by KMS while every S3 permission looked right
- retry_join verified the leader against a name no certificate carried,
so no peer could ever have joined
- the autoscaling group used ELB health before Ansible had issued
certificates, so a bare apply terminated and relaunched forever
- the root volume and the seal shared one KMS key, so destroy
scheduled the key every archived snapshot depended on
And two guards so the class stops needing an apply to find:
tests/preflight-static checks the agreements no single layer can see, and
tests/cloud-apply-emulated runs a real terraform apply against an
implementation of the AWS API.
Three of the five were held in place by passing assertions. That is
written up in the posts now linked from the docs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fifteen PRs since v0.13, with one theme: settle everything about a cloud apply that can be settled without performing one.
Five real defects
None of which the twenty-seven checks could see:
kms:GenerateDataKeyleader_tls_servernamedestroyscheduled the key every archived snapshot depended onTwo guards
tests/preflight-static— the cross-layer agreements no single layer can see: Terraform against the cloud-init it renders, that against the Ansible layer that finishes the nodetests/cloud-apply-emulated— a realterraform apply, through the real AWS provider, against an implementation of the AWS APIThe pattern worth noting
Three of the five were held in place by passing assertions — a test requiring the value that made the apply loop, one forbidding the rule the cluster needed to serve traffic, and one of mine comparing arns a mock had flattened. Written up in the posts now linked from the docs.
Once this is in,
v0.14can be tagged and the release cut.🤖 Generated with Claude Code