Skip to content

Ignore InvalidReplicationGroupState when fetching ElastiCache cluster tags - #6

Merged
karolszmndy merged 2 commits into
mainfrom
fix/elasticache-cluster-tags-invalid-replication-group-state
Aug 21, 2026
Merged

Ignore InvalidReplicationGroupState when fetching ElastiCache cluster tags#6
karolszmndy merged 2 commits into
mainfrom
fix/elasticache-cluster-tags-invalid-replication-group-state

Conversation

@karolszmndy

Copy link
Copy Markdown

Summary

  • A cache cluster node's own status can be available while its parent replication group is still creating/modifying/deleting.
  • ListTagsForResource fails against such a node with InvalidReplicationGroupState even though the row itself is valid, so treat it the same as CacheClusterNotFound: tags come back empty instead of failing the whole row.

Test plan

  • go build ./aws/... passes
  • Query aws_elasticache_cluster against a cluster whose replication group is mid-transition and confirm the row returns with empty tags instead of erroring

…luster tags

A cache cluster node can report status "available" while its parent replication group is still creating/modifying/deleting, causing ListTagsForResource to fail with InvalidReplicationGroupState even though the row itself is valid.
@karolszmndy
karolszmndy force-pushed the fix/elasticache-cluster-tags-invalid-replication-group-state branch from 08427c5 to 5398880 Compare August 21, 2026 09:22
…trail_query

golangci-lint's staticcheck now flags DescribeQueryInput.EventDataStore as
deprecated; it's still required when QueryId is a bare query ID rather than
a full query ARN, so keep passing it and suppress the warning.
@karolszmndy
karolszmndy merged commit 08c0965 into main Aug 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants