Closed bruceadams closed 7 years ago
This is a concrete change that partly addresses the wide-eyed dreams described in #7.
This is in the released wdscli
. I still want to support accepting credentials directly from an environment variable and possibly even three separate environment variables, but those are distinct from this issue.
Right now,
wdscli
always requires a path to a JSON file containing service credentials (url, username and password). For many typical uses ofwdscli
a user is only going to be interacting with a single service instance. Coming up with a clean way to allow credentials to just be there would enhance the user experience.Now credentials is always required after the subcommand:
wdscli overview my-service-credentials.json
Proposed, credentials are optional and in front of the subcommand:wdscli -c my-service-credentials.json overview
And, there is a well defined default filename for credentials, probably justcredentials.json
.