You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, KMSs are registered in certificates when the file is imported using the apiv1.Register method, for example, cloudkms is registered using this:
This allows third-party packages to import some of our stuff without the need to import extra libraries or unused functionality.
We should do the same for provisioners and DB engines. Doing this, it will make it easier to extend step-ca with new provisioners, and new DB engines. It would be also possible to create specific builds that enable only specific things.
The text was updated successfully, but these errors were encountered:
Description
Currently, KMSs are registered in certificates when the file is imported using the
apiv1.Register
method, for example, cloudkms is registered using this:certificates/kms/cloudkms/cloudkms.go
Lines 96 to 100 in 3f660ff
Then we import the supported kms engines in main.go:
certificates/cmd/step-ca/main.go
Lines 27 to 33 in 3f660ff
This allows third-party packages to import some of our stuff without the need to import extra libraries or unused functionality.
We should do the same for provisioners and DB engines. Doing this, it will make it easier to extend step-ca with new provisioners, and new DB engines. It would be also possible to create specific builds that enable only specific things.
The text was updated successfully, but these errors were encountered: