[BUG] | [Feature Request??]: Allow `fallback()` to work with 1Password plugin

[kjs3]

varlock version

0.7.2

Steps to reproduce

# .env.schema
…
# opInit(…)
…

SOME_API_KEY=fallback(op(`/path-to-vault/path-to-item/DOES_NOT_EXIST`), "abcd1234")

varlock load -> exits with error

What is expected?

If key exists in 1p, no problem, works already.
If key does not exist in 1p, SOME_API_KEY should come from the fallback() value.

What is actually happening?

varlock load throws and exits with an error.

System Info

varlock@0.7.2 and @varlock/1password-plugin@0.3.3

Any additional comments?

No response

[theoephraim]

I’m not sure if fallback() should always just accept and ignore errors, or if we should add a flag on op() that allows a missing key and returns undefined. Or perhaps an additional flag on fallback to treat errors as empty values.

[kjs3]

Seems like a flag on op() would be a good middle ground. Maybe on initOp() too if people want that as a blanket behavior.

[theoephraim]

allowMissing param now on op and initOp. Will be published shortly.