Templates variables

[maraino]

Description

This PR allows to use user variables in the templates used in step certificate create and step certificate sign.

Fixes #719

[LecrisUT]

Oh so --set simply creates an object accessed via .Insecure.User. Can't we have it that it completely overwrites any of the template data? This part is only used in step certificate so presumably the user wants much more control than step ca, so it shouldn't be "Insecure"

[maraino]

Oh so --set simply creates an object accessed via .Insecure.User. Can't we have it that it completely overwrites any of the template data? This part is only used in step certificate so presumably the user wants much more control than step ca, so it shouldn't be "Insecure"

For consistency with other commands we should keep the --set, --set-file, and .Insecure.User as they are, so you can use the same templates.

Regarding using a flag to manually edit the configuration, that's a nice option, it won't be --set but it can be something similar.

[maraino]

@LecrisUT can you add a new enhancement for that?

[LecrisUT]

With the hints from this PR, I think I can come up with something of that sort. Just need to edit data with the appropriate input. I'll see what I can do this weekend

[dopey]

lgtm

[maraino]

With the hints from this PR, I think I can come up with something of that sort. Just need to edit data with the appropriate input. I'll see what I can do this weekend

@LecrisUT using data won't work directly, because that's the information available to the template, you want something that works after rendering the template, either on the template itself (probably easier) or over the resulting x509util.Certificate or x509util.CertificateRequest.