Skip to content

Convex provisioning skips variables stored only in source .env.local #35

Description

@sieversjosua

Silvic 0.1.63 provisions an isolated Convex dev deployment and reports “Reading the source Convex environment” / “Syncing Convex environment variables”, but variables that exist only in the source workspace’s .env.local are not copied.

In SynTwin/mono this left a new Plot without R2_BUCKET, R2_ENDPOINT, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, and R2_KEY_PREFIX. ANAM_API_KEY was missing from both the Convex deployment and the local agent environment for the same reason. The repository’s setup contract intentionally resolves workspace values from both the source .env.local and the source Convex deployment.

Reproduction:

  1. Keep an env key in the primary workspace .env.local, but not in its Convex deployment.
  2. Adopt/provision a disposable Plot with an isolated Convex dev deployment.
  3. Inspect the target deployment env and the Plot .env.local.
  4. The key is absent even though provisioning completed successfully.

Expected: the provisioner should follow the repository’s env inheritance contract, or explicitly report that source-local variables were skipped. Deployment-scoped values such as R2_KEY_PREFIX still need to be derived for the target deployment rather than copied verbatim.

Impact: production-preview smoke tests for uploads, exports, avatar creation, and the local video agent fail after otherwise successful provisioning.

Workaround used: copy the shared credentials explicitly, derive development/<physical-deployment-slug> for R2_KEY_PREFIX, and restart the affected runtimes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions