-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(elasticache): InvalidReplicationGroupStateFault error #6815
Merged
MrCloudSec
merged 5 commits into
master
from
PRWLR-6097-fix-invalid-replication-group-state-fault
Feb 4, 2025
Merged
fix(elasticache): InvalidReplicationGroupStateFault error #6815
MrCloudSec
merged 5 commits into
master
from
PRWLR-6097-fix-invalid-replication-group-state-fault
Feb 4, 2025
Conversation
This file contains 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
github-actions
bot
added
the
provider/aws
Issues/PRs related with the AWS provider
label
Feb 4, 2025
HugoPBrito
added
backport-to-v3
Backport PR to the v3 branch
backport-to-v4.6
Backport PR to the v4.6 branch
backport-to-v5.2
Backport PR to the v5.2 branch
labels
Feb 4, 2025
…o PRWLR-6097-fix-invalid-replication-group-state-fault
MrCloudSec
changed the title
fix: InvalidReplicationGroupStateFault error
fix(elasticache): InvalidReplicationGroupStateFault error
Feb 4, 2025
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6815 +/- ##
==========================================
+ Coverage 88.72% 88.73% +0.01%
==========================================
Files 1195 1195
Lines 34490 34494 +4
==========================================
+ Hits 30600 30608 +8
+ Misses 3890 3886 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
MrCloudSec
approved these changes
Feb 4, 2025
MrCloudSec
deleted the
PRWLR-6097-fix-invalid-replication-group-state-fault
branch
February 4, 2025 19:28
prowler-bot
added
the
was-backported
The PR was successfully backported to the target branch
label
Feb 4, 2025
This was referenced Feb 4, 2025
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-to-v3
Backport PR to the v3 branch
backport-to-v4.6
Backport PR to the v4.6 branch
backport-to-v5.2
Backport PR to the v5.2 branch
provider/aws
Issues/PRs related with the AWS provider
was-backported
The PR was successfully backported to the target branch
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.
Context
We are facing a issue when trying to list tags for clusters/replication groups that are in certain states.
Description
This has been arranged to log a warning instead of an error.
Checklist
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.