-
Notifications
You must be signed in to change notification settings - Fork 547
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
rbd: unexport existing KMS structs for vault, AWS and KeyProtect #2750
Conversation
/retest ci/centos/upgrade-tests-rbd |
This is just a cleanup, there is no requirement in including this in 3.5.0. We should focus on other PRs that add functionality or fix bugs instead. The 3.5.0 release is already a day too late. |
This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏 |
Rebased to devel.. ptal @nixpanic |
/retest ci/centos/mini-e2e-helm/k8s-1.22 |
/retest ci/centos/mini-e2e/k8s-1.21 |
/retest ci/centos/mini-e2e-helm/k8s-1.22 |
/retest ci/centos/mini-e2e-helm/k8s-1.22 |
@nixpanic @Rakshith-R can you take a look at this ? |
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.
unexport type DEKStoreType string
, type IntegratedDEK struct{}
and type DEKStore interface
too ?
13b22d5
to
3cc45c7
Compare
@Rakshith-R done other both except the interface, which need by outside package? |
👍, there seems to be a stray file |
ah. multiple window switching .. removed it .. thanks @Rakshith-R |
1ad6c17
to
2b92647
Compare
I am wondering if there is a goal that you want to reach with this. The linked #2750 refers to this PR, and that is not helpful. Depending on the goal, |
#2725 is the correct issue link which came out of a review comment (#2723 (comment)). Corrected the link now, may be we will keep |
@nixpanic @Rakshith-R ptal.. thanks . |
At present the KMS structs are exported and ideally we should be able to work without exporting the same. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
At present the KMS structs are exported and ideally we should be able to work without exporting the same. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit unexport IntegratedDEK struct from KMS implementation Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit unexport SecretsMetadataKMS struct from KMS implementation Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit unexport VaultTenantSA struct from KMS implemenation of Vault KMS. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit unexport the vaultTokenSA from the vault KMS implementation Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
This commit unexport SecretsKMS from KMS implementation. Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
…tSA.createToken Pull-Request ceph#99 backported a commit that applies cleanly, but causes a build failure: internal/kms/vault_sa.go:313:12: kms.createToken undefined (type *VaultTenantSA has no field or method createToken) internal/kms/vault_sa.go:344:12: undefined: vaultTenantSA In recent versions, `vaultTenantSA` is used, but release-4.10 is stuck on the old naming of `VaultTenantSA`. The unexporting was done in upstream ceph#2750, which includes more changes than what we want in a backport. Signed-off-by: Niels de Vos <ndevos@redhat.com>
At present the KMS structs are exported and ideally we should be
able to work without exporting the same.
Updates #2725
Signed-off-by: Humble Chirammal hchiramm@redhat.com