Open jku opened 1 year ago
The upside of the GCP solution is that it requires no modification of the online signing workflows which is a plus: upgrading to new workflow versions is easier when they inevitably change.
The downside is that the dependency versions are now managed in this repo: I think this makes sense but I don't know if we can actually test them properly
Currently GCP KMS and Azure Key Vault are supported differently
I would like it if the workflow modification wasn't necessary. I'm not 100% sure embedding the authentication in the action itself (like we do for GCP) is the correct choice but it would be nice if the solution for both was similar