# User.toml not being picked up at /hab/user/{service}/config/user.toml

**URL:** <https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784>\
**Category:** Habitat Help\
**Created:** [June 28, 2018, 4:56pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784 "2018-06-28T16:56:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![smford22](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/smford22/32/3042_2.png) [@smford22](https://discourse.chef.io/u/smford22)\
**Post date:** [June 28, 2018, 4:56pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784/1 "2018-06-28T16:56:23Z")

</div>

Hi,

I am running hab 0.57.0/20180614230004 on Centos 7.4. I have a package called ‘compliance’ that I am trying to drop a user.toml for at `/hab/user/compliance/config/user.toml`. It was my understanding that any `user.toml` at that path will by automatically picked up by the supervisor, and that updates to that file will also be picked up. However, that is not what I am seeing. I still need to do a `hab config apply` to get that config picked up.

---

<div class="post-metadata">

**Author:** ![joshb](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshb/32/2380_2.png) [@joshb](https://discourse.chef.io/u/joshb)\
**Post date:** [June 28, 2018, 5:21pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784/2 "2018-06-28T17:21:15Z")

</div>

That’s been my experience as well, going back at least a few versions of the supervisor. I’m not certain if that was changed on purpose of it it’s a bug. I’ve gone through the open habitat issues but I can’t find anything related to this.

@christophermaier is this something you know about?

---

<div class="post-metadata">

**Author:** ![qubitrenegade](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/qubitrenegade/32/2978_2.png) [@qubitrenegade](https://discourse.chef.io/u/qubitrenegade)\
**Post date:** [June 28, 2018, 9:33pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784/3 "2018-06-28T21:33:48Z")

</div>

@smford22 are you starting the compliance service then creating the `user.toml` ?

Behavior that I’ve observed is _modifying_ an existing `user.toml` will be picked up by the hab-sup, but if you start the compliance service, then drop a `user.toml` the supervisor doesn’t pick it up, I had to restart my service.

I haven’t validated that’s the user experience with 0.57, but I was seeing the same behavior in 0.55 and 0.56.

---

<div class="post-metadata">

**Author:** ![eeyun1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/eeyun1/32/2658_2.png) [@eeyun1](https://discourse.chef.io/u/eeyun1)\
**Post date:** [July 2, 2018, 3:05pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784/4 "2018-07-02T15:05:48Z")

</div>

Yeah this is a known bug at the moment. Effectively the new “canonical” path is the one that doesn’t work. I _think_ it still works on the deprecated path of `/hab/svc/<service_name>/user.toml`.

---

<div class="post-metadata">

**Author:** ![christophermaier\_1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/christophermaier_1/32/2828_2.png) [@christophermaier\_1](https://discourse.chef.io/u/christophermaier_1)\
**Post date:** [July 27, 2018, 7:38pm UTC](https://discourse.chef.io/t/user-toml-not-being-picked-up-at-hab-user-service-config-user-toml/18784/5 "2018-07-27T19:38:17Z")

</div>

Sorry I’m late to the party… `/hab/user/<service>/config/user.toml` is indeed the path for user.toml that is watched for changes.

One thing to check is that you don’t have any config that’s being gossiped (e.g., using `hab config apply`) that would mask those changes, since they take priority over `user.toml`.