You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -183,5 +211,20 @@ echo " OK: VectorBucket is gone"
183
211
assert_gone "state file s3://${STATE_BUCKET}/${STATE_KEY} still exists after destroy" aws s3api head-object --bucket "${STATE_BUCKET}" --key "${STATE_KEY}"
184
212
echo" OK: state file is gone"
185
213
214
+
# The CMK is NOT an orphan: AWS never hard-deletes a KMS key, so a destroyed
215
+
# `RemovalPolicy.DESTROY` key lands in PendingDeletion (7-day default window)
216
+
# rather than disappearing. Assert that state explicitly so a key left ENABLED
217
+
# (a real leak — the destroy never scheduled it) still fails the run.
0 commit comments