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.
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
ROX-18431: restore deleted tenant through API #1207
ROX-18431: restore deleted tenant through API #1207
Changes from all commits
ee6d47f
45f0385
69340d1
39ba9be
c451cfd
fca1bc6
f696ade
2c7c201
ae09ba1
a470d2a
2159e81
d8893c6
3cff075
fd31c71
7431d9f
ddc6106
daf99a0
3684b90
7a05cd6
6315c1f
9047b08
b3a23c7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a side note, this will not work if the default database ID is overridden, at least the way I started to implement this here: #1198
In that PR the override is currently implemented as a ConfigMap in the data plane. Do you think the override name should actually be stored by FM?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about that. For now just assumed clusterID would be correct after #1198 in any case because I didn't know how you would handle that.
IIUC all overrides at some point should be done declaratively through GitOps. But we don't want to make the Backup/Restore epic depend on that.
One idea instead of configmap could be to use the tags you introduced to identified the clusterID. This would work as long as there is a DB running with appropriate tags. With this approach we wouldn't need a dedicated configmap to store the override, just some tags in AWS. But we would still have the problem that we loose overwrite information once a tenant was deleted. We wouldn't find a fitting final snapshot in that case.
Not sure if we're overthinking here. This is a edge case that is very unlikely to ever happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea with using the tags directly instead of the ConfigMap is worth considering either way, thanks!
I suppose we can discuss elsewhere whether this edge case should be handled automatically, or have some manual steps in an SOP. But it can definitely happen: once a DB override is in place, the restore deleted tenant operation will not work anymore.