Confusing positional parameters for get_secret about encpass.sh

[ahnick]

@etopeter So this was by design as I want this solution to be really fast and simple to use in scripts. If I'm a developer working on a script and I just want my password to be encrypted, then I don't want to necessarily have to care about scoping it to a label and coming up with a name for my password. It's simpler for the developer to just call the method and have it take care of it for him/her in that particular case. The pattern is basically the same as using method overloading (https://en.wikipedia.org/wiki/Function_overloading), which is pretty widely used. I certainly understand the argument you are making, but the main philosophy for encpass.sh is to be super lightweight and make reasonable opinionated choices for the user to achieve low friction. Once encpass.sh starts becoming more saddled with options and required fields, then it loses some of its attractiveness as a simple solution. It's definitely a trade-off.