Active System Manager Release 8.2 SDK Reference Guide

Here is an example of a class or type element inside the classes or tyes arrays:

                                 {
                                 "id": "component-linux_postinstall-1",
                                 "componentValid": {
                                 "valid": true
                                 },
                                 "name": "linux_postinstall",
                                 "type": "SERVICE",
                                 "teardown": false,
                                 "resources": [
                                 {
                                 "id": "linux_postinstall",
                                 "displayName": "Application Settings",
                                 "parameters": [
                                 {
                                 "id": "install_packages",
                                 "type": "STRING",
                                 "displayName": "Install Packages",
                                 "required": true,
                                 "requiredAtDeployment": false,
                                 "hideFromTemplate": false,
                                 "readOnly": false,
                                 "generated": false,
                                 "infoIcon": false,
                                 "maxLength": 256,
                                 },
                                 		… 
                                 ]
                                 }
                                 ]
                                 }
                              

This represents a single class or type element of the classes or types array. It exposes just a single attribute through ASM ( for readability ). But additional parameters would be added the same way.

The declaration above, if used in `classes`, when filled out with user values would be equivalent to a puppet manifest file such as:

class { 'linux_postinstall':
                                 install_packages     => '',
                                 upload_share         => '',
                                 upload_file          => 'test.sh',
                                 upload_recursive     => 'false',
                                 execute_file_command => 'bash test.sh',
                                 yum_proxy            => ''
                                 }
                                 
                                 
                              

While the declaration above, if used in `types`, when filled out with user values would be equivalent to a puppet manifest file such as:

linux_postinstall { 'unique_title':
                                 install_packages     => '',
                                 upload_share         => '',
                                 upload_file          => 'test.sh',
                                 upload_recursive     => 'false',
                                 execute_file_command => 'bash test.sh',
                                 yum_proxy            => ''
                                 }