-
Notifications
You must be signed in to change notification settings - Fork 39
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
WIP Document realm export (and sequestered organization) feature #9781
Open
touilleMan
wants to merge
1
commit into
master
Choose a base branch
from
realm-export-doc
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
AureliaDolo
reviewed
Feb 24, 2025
> to ensure the sequester service gets access to the workspace data. | ||
> | ||
> The same behavior is also triggered whenever the sequester service is revoked, this | ||
> time in order to ensure any new data added to teh workspace won't be accessible to |
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.
Suggested change
> time in order to ensure any new data added to teh workspace won't be accessible to | |
> time in order to ensure any new data added to the workspace won't be accessible to |
And from there the client CLI should be used to decrypt the workspace | ||
from realm export file and mount it as a local directory. | ||
|
||
Also note a `--timestamp=<TIMESTAMP_AS_RFC3339>` option can be privided to specify |
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.
Suggested change
Also note a `--timestamp=<TIMESTAMP_AS_RFC3339>` option can be privided to specify | |
Also note a `--timestamp=<TIMESTAMP_AS_RFC3339>` option can be provided to specify |
Comment on lines
+268
to
+269
> However it may come handy in case of a partially corrupter workspace (e.g. in case a | ||
> mallicious/buggy actor has provided corrupted keys during a realm key rotation). |
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.
Suggested change
> However it may come handy in case of a partially corrupter workspace (e.g. in case a | |
> mallicious/buggy actor has provided corrupted keys during a realm key rotation). | |
> However it may come handy in case of a partially corrupted workspace (e.g. in case a | |
> malicious/buggy actor has provided corrupted keys during a realm key rotation). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.