-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
elasticache_info: ignore CacheClusterNotFound exeption during tag collect #1777
Conversation
…lect If we call `get_elasticache_tags_with_backoff()` on a cluster with an invalid state (eg: deleting), AWS will trigger an `CacheClusterNotFound`. With this change, `elasticache_info` will ignore the cluster and continue with the next one.
50ac98f
to
c972ed7
Compare
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 05s |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 3m 39s |
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #1778 🤖 @patchback |
…lect (#1777) elasticache_info: ignore CacheClusterNotFound exeption during tag collect If we call get_elasticache_tags_with_backoff() on a cluster with an invalid state (eg: deleting), AWS will trigger an CacheClusterNotFound. With this change, elasticache_info will ignore the cluster and continue with the next one. Reviewed-by: Mark Chappell (cherry picked from commit 5461b2e)
…lect (#1777) (#1778) [PR #1777/5461b2e2 backport][stable-5] elasticache_info: ignore CacheClusterNotFound exeption during tag collect This is a backport of PR #1777 as merged into main (5461b2e). If we call get_elasticache_tags_with_backoff() on a cluster with an invalid state (eg: deleting), AWS will trigger an CacheClusterNotFound. With this change, elasticache_info will ignore the cluster and continue with the next one. Reviewed-by: Mark Chappell
Thank you @tremble :-). |
If we call
get_elasticache_tags_with_backoff()
on a cluster with an invalidstate (eg: deleting), AWS will trigger an
CacheClusterNotFound
.With this change,
elasticache_info
will ignore the cluster and continue withthe next one.