fly secrets import double-quoting behavior (KEY="VALUE")

I was writing up instructions on deploying something to fly and ended up doing:

$ fly secrets import

And the secret’s value was set to "VALUE" rather than VALUE.

As a user, this is somewhat confusing. I use .envrc files which are glorified shell scripts, but even for folks using the simpler .env files, various tools accept quoting, like Docker: Declare default environment variables in file | Docker Documentation

Possible resolutions include: accepting (and unescaping) double-quoted values, documenting the behavior of flyctl here, closing as WONTFIX :stuck_out_tongue: