Vercel Add-on unexpectedly merges outdated values back to vault #349
Description
I was trying to deploy my updated .env.staging to Vercel via the add-on, with some new values and some updated values. npx dotenv-vault@latest push staging updated my variables, which was reflected in the web console. I then manually triggered the Vercal add-on (automated add-on triggering has not been reliable).
Expected behavior: Vercel environment variables mirror the values in the latest vault I pushed, and any variables I deleted in my vault are removed from Vercel.
Actual behavior: Existing variables in Vercel are unchanged, new variables are added. My vault is changed to include the older values, replacing the values I had updated and adding back the ones I had removed.
If this is intended behavior, it's not what I expected and is pretty confusing.