-
Notifications
You must be signed in to change notification settings - Fork 67
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
SCB-1563: Support for encrypting values #55
base: master
Are you sure you want to change the base?
Conversation
拉取主分支最新功能
rootCAFile: /opt/kie/ca.crt |
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.
不要提交ca上来
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.
主分支已经存在,是 #20 合并进来的,确定要删除吗?
server/service/crypto_service.go
Outdated
service KV | ||
} | ||
|
||
func (ckv *cryptoKV) CreateOrUpdate(ctx context.Context, kv *model.KVDoc) (*model.KVDoc, error) { |
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.
不需要重新写一个实现,而是将加解密过程作为一个中间层,在kv创建更新查询流程中处理,这整个文件都是不需要的
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.
这样就需要写到两个具体实现里面,
github-projs/servicecomb-kie/server/service/mongo/history/service.go
github-projs/servicecomb-kie/server/service/mongo/kv/kv_service.go
这样如果后面换了存储实现(比如 consul,mysql 等),再次实现这个 service 的时候也需要加上加密的相关实现,这样会增加和底层 service 的耦合度及其实现难度。所以我建议对加密形成一个中间代理层,这个代理层里面的对加密的实现其实和底层的存储无关
感谢你的贡献,请看下comment,提出你的意见 |
No description provided.