# Dvc.yaml: \`deps\` & \`outs\` section accessible from code?

**URL:** <https://discuss.dvc.org/t/dvc-yaml-deps-outs-section-accessible-from-code/577>\
**Category:** Questions\
**Created:** [December 8, 2020, 9:35pm UTC](https://discuss.dvc.org/t/dvc-yaml-deps-outs-section-accessible-from-code/577 "2020-12-08T21:35:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![rabefabi](https://avatars.discourse-cdn.com/v4/letter/r/74df32/32.png) [@rabefabi](https://discuss.dvc.org/u/rabefabi)\
**Post date:** [December 8, 2020, 9:47pm UTC](https://discuss.dvc.org/t/dvc-yaml-deps-outs-section-accessible-from-code/577/2 "2020-12-08T21:47:19Z")

</div>

Hm, after browsing the forum a bit more I feel silly, seems like a similar question was just discussed a couple days ago: [Parameterlike dependencies](https://discuss.dvc.org/t/parameterlike-dependencies/565/5) .

If I understand this question and [the docs](https://github.com/iterative/dvc/wiki/Parametrization) correctly, I can specify the paths in the _params.yaml_, and have the DVC Pipeline track the values of these parameters as deps/outs:

_dvc.yaml_:

```auto
stages:
  preprocess:
    cmd: python src/preprocess.py
    deps:
      - ${raw_path}
      - src/preprocess
    outs:
      - ${preprocessed_path}

```

_params.yaml_

```auto
raw_path: "data/raw"
preprocessed_path: "data/preprocessed"

```

Just tried it in a small project, and is obviously a better solution than my proposed “named dependencies” from above.

Looking forward to the release!

---

_[View the full topic](https://discuss.dvc.org/t/dvc-yaml-deps-outs-section-accessible-from-code/577)._