# How to define pipeline parameters in dynamic config

**URL:** <https://discuss.circleci.com/t/how-to-define-pipeline-parameters-in-dynamic-config/46103>\
**Category:** Build Environment\
**Tags:** dynamic-config\
**Created:** [November 14, 2022, 12:54pm UTC](https://discuss.circleci.com/t/how-to-define-pipeline-parameters-in-dynamic-config/46103 "2022-11-14T12:54:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vanals](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vanals/32/28585_2.png) [@Vanals](https://discuss.circleci.com/u/Vanals)\
**Post date:** [November 14, 2022, 12:54pm UTC](https://discuss.circleci.com/t/how-to-define-pipeline-parameters-in-dynamic-config/46103/1 "2022-11-14T12:54:33Z")

</div>

Hi

I need to set up a parameter using the dynamic config and set it equal to a value based on a script.

I could see in the [Dynamic config documentation](https://circleci.com/docs/using-dynamic-configuration/) that it is possible to declare and define pipeline variables using the `path-finder orb` based on file changes. But it doesn’t really fit my needs, I don’t need to check what has changed and is overkilling having to use that orb for what I need.

Basically, I would need something like:

```auto
version: 2.1

# this allows you to use CircleCI's dynamic configuration feature
setup: true

orbs:
  continuation: circleci/continuation@0.1.2

define-pipeline-parameter:
  executor: node
  steps:
    # THIS doesn't rly exist, made it myself
    - set-param: |
        pipeline-param-1 $(echo git log and something else)
    - continuation/continue:
        configuration_path: generated_config.yml # use newly generated config to continue

workflows:
  setup:
    jobs:
      - define-pipeline-parameter

```

Then trigger a workflow or not based on pipeline-param-1.

How can I achieve that? Dynamic config sounds agreat concept by seems by the docs is chained to the “repo changes” concept.

PS: Ofc if I can do define a pipeline param as such, without using Dynamic config would be great too, but using the pipeline don’t think would do it. This pipeline is the outcome of a github pr

---

<div class="post-metadata">

**Author:** ![Vanals](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/vanals/32/28585_2.png) [@Vanals](https://discuss.circleci.com/u/Vanals)\
**Post date:** [November 16, 2022, 4:59pm UTC](https://discuss.circleci.com/t/how-to-define-pipeline-parameters-in-dynamic-config/46103/2 "2022-11-16T16:59:38Z")

</div>

I have solved my issue using dynamic config.  
Grabbed whatever data I needed,  
Saved the data into a .json file

```auto
 echo "$PARAMETERS" >> "circle-ci-setup-parameters.json"

```

used the circleci/continuation@0.1.2 orb to pass the new defined parameter

```auto
      - continuation/continue:
          configuration_path: ./.circleci/continue_config.yml
          parameters: ./circle-ci-setup-parameters.json

```

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [November 26, 2022, 5:00pm UTC](https://discuss.circleci.com/t/how-to-define-pipeline-parameters-in-dynamic-config/46103/3 "2022-11-26T17:00:29Z")

</div>

Closed on November 26, 2022, 5:00pm UTC

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.