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.

Sign up for GitHub

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

Jump to bottom

<running>/<intended> MUST ALWAYS be valid #4

Open

QiufangMa opened this issue Dec 24, 2024 · 0 comments

QiufangMa commented Dec 24, 2024 •

edited

Loading

This “MUST always” is probably too strong and does not consider some cases (e.g., software upgrade), some comments from Rob:

I think that there are certain actions, e.g., software upgrade where systems may struggle to guarantee that always stays valid, and one valid option for handling this is to allow it to become invalid, and then require the first edit-config/edit-data operation to get <running>/<intended> back to being a valid datastore again.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment