Skip to content
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

Remove keys on CRS cache miss #1162

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

HDauven
Copy link
Member

@HDauven HDauven commented Nov 29, 2023

Resolves #825

In case of a CRS cache miss, the keys folder will be removed.

This does not catch the situation in which someone replaces the CRS with another one.

@HDauven HDauven marked this pull request as ready for review November 29, 2023 17:12
Copy link
Member

@herr-seppia herr-seppia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if recovery is invoked using "keep_keys"? You should avoid to delete them, or delete only the used ones

@HDauven
Copy link
Member Author

HDauven commented Nov 30, 2023

What if recovery is invoked using "keep_keys"? You should avoid to delete them, or delete only the used ones

Are we sure that, in the case of "keep_keys" being used, but the CRS missing after a rerun of recovery, we still want to keep the keys? I don't know of a situation where that would be useful or make sense.

The removal of the keys folder would happen in the unhappy flow of the lambda.

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.

Keys can be generated from two different CRS
2 participants