cc path no longer regex

[yphoenix]

See: #1793

search 'VA AWS (yorick)'

  #  Record UID              Type    Title                     Description
---  ----------------------  ------  ------------------------  -----------
  1  XXXXXXXXXXXXXXXXXXXXXX  login   VA AWS (yorick)           XXXXXXX
  2  XXXXXXXXXXXXXXXXXXXXXX  login   VA GovCloud AWS (yorick)  XXXXXXX

search --regex 'VA AWS (yorick)'

  #  Record UID              Type    Title                     Description
---  ----------------------  ------  ------------------------  -----------
  1  XXXXXXXXXXXXXXXXXXXXXX  login   VA AWS (yorick)           XXXXXXX

That solved it for search but really I trying to use it with cc

cc 'VA AWS (yorick)'
More than one record are found for search criteria: VA AWS (yorick)

Because the search there is now "relaxed" and not regex anymore, the problem will crop up everywhere that the "record path" can be specified.

How do I solve that, other that performing a search, and then using the results of the search as the UID for the cc command.

Thanks

[yphoenix]

While I understand the thinking of "lets make record name matching work the same as the application" I'm not sure that it is a good idea. The CLI should be precise and changing the functionality breaks existing scripts - like it broke ours today and we reverted to a working version. Also, with the app or the SuperShell you have a UI, if you match multiple items, that's OK, the user can interact and choose. The CLI in this environment is not interactive.

Maybe the solution is to add a flag to indicate that you want relaxed matching, or use relaxed matching with any UI interface, but if the output is piped, or set to a variable, copied to the clipboard etc then it should be regex.

Alternatively add a -exact-match option, or if the pattern is in quotes, or something that means you can have it either way. At the moment it changes quite often with a new release and I have to keep adjusting our scripts to match.

Thanks

[yphoenix]

Not fixed in 17.2.7

[craiglurey]

Hi, sorry for the issue with the search command. We actually added a --regex flag so you should be able to use:
search --regex 'VA AWS (yorick)'

Let me know if this resolves it.

[yphoenix]

The problem is with the cc command, and probably all other commands that allow you to specify a path. Only the search command has the --regex option. If you add it to all commands then that would solve things.

[craiglurey]

What's the issue with cc? this didn't change. Please be as specific as possible.

[yphoenix]

I thought I was clear earlier, but more than willing to explain it again...

Given that I have two records:

  #  Record UID              Type    Title                     Description
---  ----------------------  ------  ------------------------  -----------
  1  XXXXXXXXXXXXXXXXXXXXXX  login   VA AWS (yorick)           XXXXXXX
  2  XXXXXXXXXXXXXXXXXXXXXX  login   VA GovCloud AWS (yorick)  XXXXXXX

I used to do:

cc  --totp --output=stdout  'VA AWS \(yorick\)'

=> NNNNNN - it matched record #1, perfect.

From 17.2.6 onwards

cc --totp --output=stdout 'VA AWS \(yorick\)'

=> Enter name or uid of existing record - so no matches.

And if I try:

cc --totp --output=stdout 'VA AWS (yorick)'

=> More than one record are found for search criteria: VA AWS (yorick) - multiple matches

Thus my conclusion is that cc matching now works exactly like search matching, except you can't specify a regex anymore and even if I'm wrong about why the matching doesn't work, it doesn't work the way it used it (pre 17.2.6).

NB: We appreciate all the great work everyone does on the Keeper CLI, it's frustrating when things change so the point that we can't fix our scripts to make them work again.

[craiglurey]

Thank you, that looks like a bug introduced in the change, we will address it.

[yphoenix]

Thank you.

[craiglurey]

Please check the "release" branch, it has the commits

[yphoenix]

Thanks, tried, but ran into to conflicts setting up from source (I'm on macOS). Can try again later.