feat(declarativeSettings): support sensitive Declarative settings values encryption #585
Conversation
This file contains hidden or 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
|
In context agent we use I guess, that decryption for sensitive values should be added there as well? |
Yes, also |
andrey18106
force-pushed
the
feat/sensitive-declarative-settings
branch
from
874e8aa to
f22a057
Compare
andrey18106
force-pushed
the
feat/sensitive-declarative-settings
branch
from
f22a057 to
f152c62
Compare
kyteinsky
reviewed
May 29, 2025
oleksandr-nc
approved these changes
May 29, 2025
Signed-off-by: Andrey Borysenko <[email protected]>
andrey18106
force-pushed
the
feat/sensitive-declarative-settings
branch
from
54755b1 to
819f104
Compare
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.
Related to: nextcloud/server#53121
Implement sensitive Declarative settings encryption for ExApps.