Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Active System Manager Release 8.2 SDK Reference Guide

PDF

Module Dependencies

Access to the ASM appliance could allow one to load Puppet modules on the Puppet master. But barring login access, any Puppet module dependencies must be uploaded to ASM in the same way as the application module that depends on them. That is to say, for each dependency module we must add an asm_input.json file to the Puppet module, zip it, and then upload it to ASM in order to satisfy the dependency.

For example, puppetlabs-apache depends on the module puppetlabs-concat. So, to utilize puppetlabs-apache, we would have to first upload the puppetlabs-concat module.

Typically the dependency modules will not be used explicitly, so they can be simplified by leaving the classes and types arrays mostly empty. However, at least one class or resource must be declared in one of the classes or types arrays. A convenient way to satisfy this requirement is to declare a notify resource in the types array.

In fact, the generator script will do just this, by supplying the –-dependency argument to the generator script:

generate_asm_module.rb --dependency


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\