Skip to content

Filter AWS-managed ElastiCache defaults from e2e aws-nuke - #598

Merged
melanie-exygy merged 1 commit into
mainfrom
melanie-exygy/ignore-ElastiCache-users
Sep 30, 2026
Merged

melanie-exygy merged 1 commit into
mainfrom
melanie-exygy/ignore-ElastiCache-users

Conversation

@melanie-exygy

@melanie-exygy melanie-exygy commented Sep 30, 2026 •

Copy link
Copy Markdown
Contributor

Description

This fixes the failing e2e-test GH job. Since 2026-09-29, AWS auto-creates the ElastiCache user default.iam-user and user group default.iam-user-group. They can't be deleted because the "." isn't an accepted character in the resource name, so aws-nuke fails on both the pre and post nuke steps. Filter them out until aws-nuke handles them itself (ekristen/aws-nuke#1039).

Checklist

General

  • Added the correct label
  • Assigned to a specific person or civiform/deployment-system
  • Created tests which fail without the change (if possible)
  • Performed manual testing (at a minimum run bin/setup without your changes and then bin/deploy with your changes to ensure your changes don't break existing deployments)
  • Extended the README / documentation, if necessary

Issue(s) this completes

Fixes #14058

Since 2026-09-29, AWS auto-creates the ElastiCache user default.iam-user
and user group default.iam-user-group. They can't be deleted, so aws-nuke
fails on both the pre and post nuke steps. Filter them until aws-nuke
handles them itself (ekristen/aws-nuke#1039).
@melanie-exygy melanie-exygy added the bug Something isn't working label Sep 30, 2026
@melanie-exygy
melanie-exygy merged commit 0a4e0a8 into main Sep 30, 2026
9 checks passed
@melanie-exygy
melanie-exygy deleted the melanie-exygy/ignore-ElastiCache-users branch September 30, 2026 16:08
@melanie-exygy melanie-exygy mentioned this pull request Sep 30, 2026
16 of 23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants