# CircleCI Integration using branch configs and service tokens

**URL:** <https://community.doppler.com/t/circleci-integration-using-branch-configs-and-service-tokens/796>\
**Category:** Need Help\
**Created:** [October 10, 2022, 1:22am UTC](https://community.doppler.com/t/circleci-integration-using-branch-configs-and-service-tokens/796 "2022-10-10T01:22:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![discostew](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/discostew/32/558_2.png) [@discostew](https://community.doppler.com/u/discostew)\
**Post date:** [October 10, 2022, 1:22am UTC](https://community.doppler.com/t/circleci-integration-using-branch-configs-and-service-tokens/796/1 "2022-10-10T01:22:41Z")

</div>

When performing CircleCI Integration using branch configs and service tokens, I can see my variables in the CircleCI logging by adding the line:

```auto
- run:
          name: Test Doppler secrets access
          command: doppler run --token $DOPPLER_TOKEN_PREVIEW -- printenv | grep {Name of an ENV secret} # Testing purposes only

```

So I know that the data has been loaded into the Circle CI Docker engine.

Are these ENV variables now fully available as if they were in the CircleCI Environment Variables entry?

Or do I need to instead of running:

```auto
yarn build

```

in my `config.yml` , do I need to run

```auto
doppler run yarn build

```

?

---

<div class="post-metadata">

**Author:** ![discostew](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/discostew/32/558_2.png) [@discostew](https://community.doppler.com/u/discostew)\
**Post date:** [October 11, 2022, 5:04pm UTC](https://community.doppler.com/t/circleci-integration-using-branch-configs-and-service-tokens/796/2 "2022-10-11T17:04:48Z")

</div>

My problem was I wasn’t understanding that each `doppler run` command was ephemeral for each execution.

Also, if your `build` config is setup to look for a .env file, you need to use the `--mount` command to create an ephemeral .env file for your build step.

`doppler run --token ${DOPPLER_DEV} --mount .env yarn build`