# Pass metadata to triggered pipelines with pure YAML

**URL:** <https://forum.buildkite.community/t/pass-metadata-to-triggered-pipelines-with-pure-yaml/875>\
**Category:** Features Requests\
**Created:** [January 21, 2020, 6:45pm UTC](https://forum.buildkite.community/t/pass-metadata-to-triggered-pipelines-with-pure-yaml/875 "2020-01-21T18:45:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![carl](https://avatars.discourse-cdn.com/v4/letter/c/ee7513/32.png) [@carl](https://forum.buildkite.community/u/carl)\
**Post date:** [June 26, 2020, 8:28am UTC](https://forum.buildkite.community/t/pass-metadata-to-triggered-pipelines-with-pure-yaml/875/2 "2020-06-26T08:28:32Z")

</div>

+1 to this - we have a lot of pipelines which trigger other pipelines with dynamic metadata.

e.g:

```auto
steps:
  - command: "create_deployment.sh" # sets deployment-name metadata

  - wait: ~

  # script which reads metadata + uploads trigger step below
  - command: "profile_deployment.sh" 

```

```auto
  - trigger: "deployment-profiling"
    build:
       meta_data:
          # has to be resolved by script, doesnt work in steps.yaml
          deployment-name: $(buildkite-agent meta-data get deployment-name) 

```

It would be ideal if we could remove the `profile_deployment.sh` script and just directly put that trigger step into the yaml

---

_[View the full topic](https://forum.buildkite.community/t/pass-metadata-to-triggered-pipelines-with-pure-yaml/875)._