Skip to content

Do not delete phantom if exists and ShadowCopy is OFF #2955

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

Closed
wants to merge 2 commits into from

Conversation

ltorje1
Copy link

@ltorje1 ltorje1 commented Aug 2, 2024

Closes #2954

@pivotal-cla
Copy link

@ltorje1 Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-cla
Copy link

@ltorje1 Thank you for signing the Contributor License Agreement!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 2, 2024
christophstrobl pushed a commit that referenced this pull request Aug 6, 2024
This commit makes sure to consider the ShadowCopy flag for expiring key events and prevents delete attempts if shadow copy is off.

Closes: #2954
Original Pull Request: #2955
christophstrobl added a commit that referenced this pull request Aug 6, 2024
Move reading shadow copy to dedicated method, update GH issue references, add test and fix formatting.

Original Pull Request: #2955
@christophstrobl
Copy link
Member

christophstrobl commented Aug 6, 2024

Thank you for your contribution @ltorje1. Merged to main development line via 3e80819.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

If ShadowCopy is OFF do not use the phantom key
5 participants