# Avoid daemon module re-configuration after redeploy

**URL:** <https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [October 23, 2019, 10:22am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513 "2019-10-23T10:22:42Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mykyta](https://avatars.discourse-cdn.com/v4/letter/m/7cd45c/32.png) [@Mykyta](https://community.bloomreach.com/u/Mykyta)\
**Post date:** [October 23, 2019, 10:22am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/1 "2019-10-23T10:22:42Z")

</div>

Hello everyone.

I noticed that after re-deploy, the configuration of Deamon Module takes configuration from yaml file that is stored in code base and reset all properties that were before re-deploy. It is not applicable for us behaviour as this configuration is environment specific, so can not be stored in code base.

Is it possible to forbid re-configuration of Demon Module after re-deploy with default properties?

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [October 23, 2019, 10:48am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/2 "2019-10-23T10:48:26Z")

</div>

You can mark that configuration as system.

> **[Categorization - BloomReach Experience - Open Source CMS](https://documentation.bloomreach.com/library/concepts/configuration-management/categorization.html)**
>
> Open Source Enterprise Content Management

---

<div class="post-metadata">

**Author:** ![bcanvural](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/bcanvural/32/235_2.png) [@bcanvural](https://community.bloomreach.com/u/bcanvural)\
**Post date:** [October 23, 2019, 11:31am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/3 "2019-10-23T11:31:33Z")

</div>

Isn’t “content” more appropriate ? you want the definition to be loaded only once. If the definition already exists it shouldn’t be reloaded

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [October 23, 2019, 1:20pm UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/4 "2019-10-23T13:20:19Z")

</div>

content may be more appropriate.

---

<div class="post-metadata">

**Author:** ![Mykyta](https://avatars.discourse-cdn.com/v4/letter/m/7cd45c/32.png) [@Mykyta](https://community.bloomreach.com/u/Mykyta)\
**Post date:** [October 24, 2019, 10:16am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/5 "2019-10-24T10:16:16Z")

</div>

@bcanvural, @jasper.floor Thanks for the replies!

I achieved desired result by adding `.meta:category: system` under each target properties in `hipposys:moduleconfig`.  
 ![image](https://canada1.discourse-cdn.com/flex027/uploads/bloomreach1/original/1X/ba5c48965bfeeb8ed662135bad945eeeffc5ba62.png)

When I was trying to add `.meta:category: content` (to the node level as content is not supported for properties) I was getting an exception during repository initialization.

Probably I missed something but is there way to configure `hipposys:moduleconfig` (once, in the top level) to avoid reloading all child properties in all child config nodes?

---

<div class="post-metadata">

**Author:** ![bcanvural](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/bcanvural/32/235_2.png) [@bcanvural](https://community.bloomreach.com/u/bcanvural)\
**Post date:** [October 24, 2019, 12:39pm UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/6 "2019-10-24T12:39:54Z")

</div>

Hey @Mykyta,  
Can you try the following?

```auto
  config:
    /hippo:configuration/path/to/your/node:
      .meta:residual-child-node-category: content

```

In some projects I use this to mark users as content for example:

```auto
    /hippo:configuration/hippo:users:
      .meta:residual-child-node-category: content

```

---

<div class="post-metadata">

**Author:** ![Mykyta](https://avatars.discourse-cdn.com/v4/letter/m/7cd45c/32.png) [@Mykyta](https://community.bloomreach.com/u/Mykyta)\
**Post date:** [October 28, 2019, 8:17am UTC](https://community.bloomreach.com/t/avoid-daemon-module-re-configuration-after-redeploy/1513/7 "2019-10-28T08:17:42Z")

</div>

Thanks @bcanvural for the advice.  
`.meta:residual-child-node-category: content` works when I am trying to create new child nodes, but not for properties in existed nodes.  
Also I noticed in [Categorization Article](https://documentation.bloomreach.com/library/concepts/configuration-management/categorization.html):

> There is no equivalent to the residual-child-node-category for properties; properties of a category other than configuration must all be categorized explicitly.

So, I am okay with using `.meta:category: system` for all properties!  
Thanks @jasper.floor, @bcanvural for the replies!