What we need to do is somehow merge this functionality into the regular key command.
We should also assume that a user may have multiple azure clouds and that the name and cloud type from the yaml file should be used to identify if the cloud is azure or not
passing the cloudnake such as --cloud=azure (if there is a named cloud azure) may be the solution
We have currently a command for azure key management that is as follows::
akey add –name=key-name –pub=pub-key-path –cert=pem-certificate-file-path –pfx=pfx-file-path
What we need to do is somehow merge this functionality into the regular key command. We should also assume that a user may have multiple azure clouds and that the name and cloud type from the yaml file should be used to identify if the cloud is azure or not
passing the cloudnake such as --cloud=azure (if there is a named cloud azure) may be the solution