# Applying configuration in CD pipelines

**URL:** <https://discourse.chef.io/t/applying-configuration-in-cd-pipelines/19361>\
**Category:** Habitat Community\
**Created:** [August 13, 2018, 5:38pm UTC](https://discourse.chef.io/t/applying-configuration-in-cd-pipelines/19361 "2018-08-13T17:38:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![elliott-davis](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/elliott-davis/32/2146_2.png) [@elliott-davis](https://discourse.chef.io/u/elliott-davis)\
**Post date:** [August 13, 2018, 5:38pm UTC](https://discourse.chef.io/t/applying-configuration-in-cd-pipelines/19361/1 "2018-08-13T17:38:52Z")

</div>

All configuration changes in Habitat are scoped to a service group Ex: `logstash.default`. In general, if you wish to apply configuration to a service that exists in a particular channel, you should set the channel and the group to the same name. This will give you many service groups but that is exactly what they are designed to do, segment your service based on environment. So in this example we could have `logstash.acceptance` watching channel `acceptance`. You would then apply configuration to the `logstash.acceptance` group.

@tnargnai @adam sound legit?