allowMissing for Infisical

[philmillman]

Summary

Adds allowMissing to @varlock/infisical-plugin, matching the behavior already shipped for 1Password in #586.

Closes #875.

When allowMissing is truthy, Infisical 404 / not-found errors resolve to undefined instead of throwing. That makes optional Infisical-backed secrets work with Varlock's normal composition tools (fallback(), @required=false, forEnv(), etc.). Auth failures, permission errors, and other non-not-found errors still throw.

• infisical(allowMissing=true) — per-call override
• @initInfisical(allowMissing=...) — instance-level default (supports dynamic values like forEnv(development))
• Per-call allowMissing overrides the instance default

Example

# @initInfisical(
#   projectId=$INFISICAL_PROJECT_ID,
#   environment=dev,
#   clientId=$INFISICAL_CLIENT_ID,
#   clientSecret=$INFISICAL_CLIENT_SECRET
# )
# ---

# Optional provider secret: use Infisical when present, otherwise undefined
RESEND_API_KEY=fallback(infisical(allowMissing=true), undefined)

[github-actions]

The changes in this PR will be included in the next version bump.

Minor releases

• @varlock/infisical-plugin 2.0.1 → 2.1.0

Bump files in this PR

• infisical-allow-missing.md (view diff) (edit)

Click here if you want to add another bump file to this PR

---

This comment is maintained by bumpy.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	varlock-website	24af6bb	Commit Preview URL Branch Preview URL	Jul 11 2026, 02:41 PM

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@varlock/infisical-plugin@878

commit: 24af6bb

[theoephraim]

lgtm - we may want to think about solving this in a more generalized way rather than per plugin, but it might be hard to do that... So likely just doing it per plugin for now