I’ve worked out the issue.
My .env file included:
SITE_NAME=Common Guide
When I go to import this manually via the admin interface, it generates an error:
Sure enough, by removing an attempt to set SITE_NAME in my .env it then works.
Based on this, I’d now like to report a explicit bug.
Running netlify env:import .env silently fails when a reserved environment variable is included in the .env file.
To correct the bug:
The command should return an explicit fail and provide the same warning that is shown in the visual interfacet.
Something like this:
$ netlify env:import .env
Import failed. Reason: SITE_NAME is a reserved environment variable. Remove reserved variables from file and retry.
Please raise a ticket.
