Puppet services can be used to build application blueprints. You must import Puppet modules and defined resources into the Application Services library as services.

About this task

You can import multiple Puppet modules at the same time.

After you import the Puppet modules, these services have a special tag called Puppet Services. The newly imported services do not have action scripts. Application Services delegates their life cycle activities to the registered Puppet Master instance in the corresponding deployment environment.

The imported Puppet content cannot be updated. You can remove the service or change the existing Puppet service version and import the updated Puppet content into the library. The default version is 1.0.0-unknown for Puppet modules with missing version information.


  • Log in to Application Services as an application cloud administrator and an application publisher and deployer.

  • Start the Application Services CLI. See Start the CLI Remotely.

  • The remote machine that you use to run the CLI must have Puppet modules installed and the Puppet CLI available.

    You can also use a Puppet Master machine to maintain the Puppet modules on two different machines.

  • Verify that the Puppet services you are importing are available on the Puppet Master.


After you log in to the CLI program and in the roo shell, enter the command to import the Puppet module such as Apache.

import-puppet-manifest --typeFilter "^apache$" --targetGroup pubs

The parameters in the command are case sensitive. If you use the incorrect case, the command is ignored.




Limits the import to types matching the specified search expression.

For details about expression syntax refer to the Puppet documentation or type puppet man resource_type to view the man pages. For example, to import the mysql module, type import-puppet-manifests --typeFilter "^mysql$".


Specifies the operating system for the imported type. The options are WINDOWS and LINUX.

Linux is the default operating system.


Specifies the location of the Puppet binary file.


Indicates whether the artifact is shared or private.

You can define true or false in the command. The default setting false indicates that the artifact is private to the user's group performing the import operation.


Specifies the business group for the imported manifests. This is the owning business group of the service.


The command imports the apache Puppet module to the library.

What to do next

Add the Puppet content to a new or existing application blueprint from the Puppet Services section of the blueprint canvas and deploy the application. See Create an Application and Setting Up and Configuring a Deployment Profile.