# Elastic/logstash puppet forge module config\_dir not being set

**URL:** <https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566>\
**Category:** Logstash\
**Created:** [July 24, 2020, 8:05pm UTC](https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566 "2020-07-24T20:05:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgutshal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cgutshal/32/34275_2.png) [@cgutshal](https://discuss.elastic.co/u/cgutshal)\
**Post date:** [July 24, 2020, 8:05pm UTC](https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566/1 "2020-07-24T20:05:14Z")

</div>

I am working with the following module in puppet forge:

> **[Puppet module elastic/logstash](https://forge.puppet.com/elastic/logstash)**
>
> Module for managing and configuring Logstash

This is my current profile: [https://gist.github.com/cgutshal/116d2cfd1bd21b9083088bfbacd1a804](https://gist.github.com/cgutshal/116d2cfd1bd21b9083088bfbacd1a804)

The issue I am running into is that while my pipeline configs are places in /data/logstash/conf/conf.d/ as expected, the other config files are still created in /etc/logstash regardless of if I define it as follows in my profile.

```ruby
  $base_dir = '/data/logstash'

  file { $base_dir:
    ensure => 'directory',
    group => $config['group'],
    owner => $config['user']
  }

  class { 'logstash':
    config_dir => "${base_dir}/conf", #THIS ISN'T WORKING
    ...
  }

```

Not sure what I might be doing wrong that isn't causing this to work as documented, and if there is additional info I can provide let me know. Hoping I just missed something simple.

Any help is appreciated.

Thanks

---

<div class="post-metadata">

**Author:** ![kelk](https://avatars.discourse-cdn.com/v4/letter/k/13edae/32.png) [@kelk](https://discuss.elastic.co/u/kelk)\
**Post date:** [July 27, 2020, 7:23am UTC](https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566/2 "2020-07-27T07:23:15Z")

</div>

how are you running logstash?  
what's the error you getting?

In my experience, it is better to run with path.settings to see

```auto
./bin/logstash --path.settings /data/logstash

```

---

<div class="post-metadata">

**Author:** ![cgutshal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cgutshal/32/34275_2.png) [@cgutshal](https://discuss.elastic.co/u/cgutshal)\
**Post date:** [July 27, 2020, 2:33pm UTC](https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566/3 "2020-07-27T14:33:18Z")

</div>

Logstash is being ran via a puppet manifest. The issue is not that I am having errors, its that documentation for the puppet module authored by elastic doesn't seem to work as described, unless I am missing something. Setting **config\_dir** to **/data/logstash/conf** does not work it is still setting it to **/etc/logstash/**.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 24, 2020, 2:36pm UTC](https://discuss.elastic.co/t/elastic-logstash-puppet-forge-module-config-dir-not-being-set/242566/4 "2020-08-24T14:36:49Z")

</div>

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