<p>A configuration management tool is not required to manage a PAAS. For example, when one has created a VM on Azure then it is possible to export the configuration snippet as powershell or as yaml and use yaml to deploy and manage systems.</p>

<p>In my opinion one should restrict configuration management tools like puppet or ansible to manage configuration files and installing additional packages and yaml to manage the PAAS as I prefer KISS.</p>

<p>If one would like to manage different PASS then one could consider to use terraform.</p>

CC BY-SA 3.0
2017-09-30T10:11:07.717Z
A vm is a IAAS, infrastructure, a platform include the middleware and its specific configuration, Java ops tailored to your app for a tomcat for example
Tensibai
CC BY-SA 3.0
2017-09-29T20:41:36.263Z
2017-09-29T20:41:36.263Z
030
<p>Modern configuration management tools can do a wide variety of things, so you can certainly use them to manage a PaaS. But it makes more sense to use a tool like <a href="https://www.terraform.io/docs/providers/heroku/index.html" rel="nofollow noreferrer">Terraform</a> to handle provisioning, since that's its specialty.</p>

CC BY-SA 3.0
2017-10-13T19:24:42.323Z
2017-10-13T19:24:42.323Z
Xiong Chiamiov
<p>ARM Templated Deployment for the PaaS and the underlying components managed by Microsoft in the case of Azure. Don’t need a seperate CM. This is the beauty of being pure PaaS. </p>

<p>terraform is a wrapper for ARM. Unless you are cross cloud no need for this. </p>

CC BY-SA 4.0
2018-05-08T12:56:27.513Z
2018-05-08T12:56:27.513Z
Venura Athukorala
<p>Is a configuration management tool (Chef/Puppet/Ansible) necessary for managing an application on a PAAS system (Azure app service, Heroku, Elastic Beanstalk)? How would it be utilized? While a tool such as Chef does not inherently work on a PAAS system, there are other tools (such as Habitat) that can support this functionality. What kind of steps would it take to integrate these technologies?</p>

<configuration-management><platform-as-a-service>
How to integrate a platform as a service with configuration management tools?
Preston Martin
# How to integrate a platform as a service with configuration management tools?

(Asked by: username_0 on 2017-09-29)

Is a configuration management tool (Chef/Puppet/Ansible) necessary for managing an application on a PAAS system (Azure app service, Heroku, Elastic Beanstalk)? How would it be utilized? While a tool such as Chef does not inherently work on a PAAS system, there are other tools (such as Habitat) that can support this functionality. What kind of steps would it take to integrate these technologies?

**Tags:** configuration-management, platform-as-a-service


---

## 3 answers

### Answer by username_1 on 2017-09-29. Score: 2 | Accepted answer

A configuration management tool is not required to manage a PAAS. For example, when one has created a VM on Azure then it is possible to export the configuration snippet as powershell or as yaml and use yaml to deploy and manage systems.

In my opinion one should restrict configuration management tools like puppet or ansible to manage configuration files and installing additional packages and yaml to manage the PAAS as I prefer KISS.

If one would like to manage different PASS then one could consider to use terraform.

> **Comments:**
> **username_2**: A vm is a IAAS, infrastructure, a platform include the middleware and its specific configuration, Java ops tailored to your app for a tomcat for example  

---

### Answer by username_3 on 2017-10-13. Score: 2

Modern configuration management tools can do a wide variety of things, so you can certainly use them to manage a PaaS. But it makes more sense to use a tool like [Terraform](https://www.terraform.io/docs/providers/heroku/index.html) to handle provisioning, since that's its specialty.


---

### Answer by username_4 on 2018-05-08. Score: 0

ARM Templated Deployment for the PaaS and the underlying components managed by Microsoft in the case of Azure. Don’t need a seperate CM. This is the beauty of being pure PaaS.

terraform is a wrapper for ARM. Unless you are cross cloud no need for this.


---

