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

**URL:** <https://community.fly.io/t/fly-secrets-import-double-quoting-behavior-key-value/9589>\
**Category:** Questions / Help\
**Created:** [December 23, 2022, 6:35pm UTC](https://community.fly.io/t/fly-secrets-import-double-quoting-behavior-key-value/9589 "2022-12-23T18:35:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ftl-github](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/ftl-github/32/35157_2.png) [@ftl-github](https://community.fly.io/u/ftl-github)\
**Post date:** [December 23, 2022, 6:35pm UTC](https://community.fly.io/t/fly-secrets-import-double-quoting-behavior-key-value/9589/1 "2022-12-23T18:35:16Z")

</div>

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

```auto
$ fly secrets import
KEY="VALUE"
^D

```

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](https://docs.docker.com/compose/env-file/)

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