Closed nbutton23 closed 3 years ago
Looking good. We should do the same for {gcp,k8s,aws}-auth-mount
and simplify it to auth-mount
Yeah I was thinking about that. . . it gets a little complicated on how we handle the different defaults (unless you know a simple way to do that). I can play around with a few options.
Right now each auth method has its own flag:
--k8s-auth
,--aws-auth
, etc.This doesn't scale and we should migrate to an input method:
--auth-method
that takes an input for which type of auth to do (k8s/aws/gcp/azure, etc.)Also move
{gcp,k8s,aws}-auth-mount
toauth-mount
and move the existingauth-mount
toauth-path
, Whereauth-mount
is used to generate aauth-path
if not provided. The defaults forauth-mount
andauth-path
are handled during the validation of theauth-method
This is a breaking change of the API.