Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
Reading API Key from Vault with VAULT_SCOPED_READ=True in your settings file.

I was testing a new extension locally when I saw this message come up:

"Opting in to old Vault read style. This is deprecated. Please set VAULT_SCOPED_READ=True in your settings file."

However when I update my settings file to have the new scoped reading style, my self.vault.read("api_keys") no longer returns the keys from my local vault. Does anyone know if I have to reinstall my keys after updating the settings file? The docs said that for certificates the system would revert to the old location if it couldn't find it in the new, but I'm not seeing the same results for keys.

Posted 2 years ago
Votes Newest

Answers


Hey Justin, the vault path on your file system would be different once you enabled that settting. The q2 vault entrypoint should help getting your secret in the location. Or I find viewing the logs at request time which will show the full path to the location it's searching and moving it there by hand.

Posted 2 years ago
Jason Herbert
104 × 1 Administrator
164 Views
1 Answer
2 years ago
2 years ago