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
Add designated folder for extensions #1245
Conversation
This should be merged first #1233 |
okay, ping me when that is merged and I will rebase again |
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.
filesystemProvisionerStore
itself looks good but this PR introduces bunch of other changes that are not related to PR title at all. We should keep PRs small and focused for easier review process. Could you split non-related changes to separate PRs with descriptive title/description why those changes are done.
@jakolehm You are correct about the sidecar changes. I have moved them to a separate branch. Are you able to review again? |
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.
LGTM
b17c9ed
to
bdb66b8
Compare
- add extension mechinism for getting a folder to save files to - add test to make sure that extensions are being loaded - skip extension loading test Signed-off-by: Sebastian Malton <sebastian@malton.name>
This PR adds a method onto
LensExtension
for getting a unique path to a folder that the extension can use for its own purposes.The folder is based on the extension ID but is not passed in so it cannot be faked. The folder name is salted and then hashed to obfuscate it and the mapping is stored in a lens store which is, by design, not otherwise exposed to extension writers. This is done so that the folder's name is not able to be determined without calling this function.
No security is applied to these folders.
fixes #1179