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
 
Unanswered
← Vendor Config vs Partner Config

Hello,

The Vendor configs are a per FI installation config(so a config for staging and production if the extension is installed more than once into the same environment though you could have 2 or more configs for the same environment), you can still have the ability to update them via self service(depending on the FI, but almost always the answer is yes). There isn't really a global service config for SDK services currently. Though, that would be an interesting idea.

Hope this helps,
Trey Teter
Software Engineer

Posted one year ago
Trey Teter
489 × 4 Administrator
0

Hi Trey, thanks for clarifying. For a multi-tenant SSO handler, I get that FIs manage vendor_configs via Self-Service (with defaults on the handler class in dev env). My key question is about our partner-owned global data in settings.py. And to confirm, must we redeploy the entire extension to update settings.py, since there's no partner self-service mechanism? Thanks.

— Eric Yan   one year ago
0

That is correct. You can also use vault for a more global value if it doesn't change that much. You can't change it with self service currently(or maybe ever), but we can quickly change it without having to redeploy.

— Trey Teter   one year ago
27 Views
0 Answers
one year ago
one year ago