Improve auto-detect of name vs filepath for Cred/Param Sets #1217
Labels
2 - 🍕
Pizza should be eaten daily
bug
Oops, sorry!
gap
We missed a spot
help wanted
Good for someone who has contributed before
Milestone
We can/should improve the auto-detection logic used for consuming Credential and Parameter Sets on the command line, e.g.
porter install -p paramset
orporter install -p paramset.json
. Primarily, it would be great to solve the case of whether or not the argument is a named cred set or a file existing in the current directory (and sans any filepath separators).This arose via feedback from #1213:
@vdice, The examples you provided were enough to help me figure out that my issue had indeed been with the parameter auto-detection syntax.
If I have a parameter file in my working directory,
testparams.json
, then apparentlyporter upgrade -p testparams.json
will interpret testparams.json as a name. Whereas if I run
porter upgrade -p ./testparams.json
it will interpret that as a path,
and if I have testparams.json in a subdirectory (params)
porter upgrade -p params/testparams.json
will interpret as a file path.
I think this autodetection behavior is a little surprising, but I'm satisfied that the functionality I was looking for still exists. Thank you for the explanation.
Originally posted by @CSberger in #1213 (comment)
The text was updated successfully, but these errors were encountered: