UX Issue: Adding environment variables

Feedback
1

Adding environemnt variables is not straightforward anymore (I think there changed something recently):

If I want to add three environment variables, I start by entering the first, click on “Add more” and enter the second one. Now I click again on “Add more” to get the input field for the third and then enter my third env.

Now I see three environment variables and start the build process - which then fails, since only the first two envs are applied. The third env is not saved and not available in the build.
I had to click again on “Add more”, so that I now see four env fields, then all my three envs will be available.

That does NOT work:

image
image642×334 11.2 KB

That works:

image
image639×391 13.6 KB

2

Thanks for the feedback, @vercel-juriwolfde!

That is strange – I’m unable to reproduce? Could you possibly share a screencast of this behaviour so I can share it internally.

3

Sure, here is a video: https://youtu.be/mXu3bvx2Z-c

I use this public repo, which needs supabase api credentials as env, as described in the readme: GitHub - primocms/primo: Primo is a visual CMS with a built-in code editor, Svelte blocks, and static site generator.

The credentials shown in the video are of course already invalidated.

5

@pawlean any news on this?

There are a few people having this issue.
One created an issue in current deploy process is broken - see logs · Issue #397 · primocms/primo · GitHub and two wrote about it on discord: Discord