Quantcast
Channel: VMware Communities : Blog List - All Communities
Viewing all articles
Browse latest Browse all 3135

Troubleshooting for vCAC Application Director import-puppet-manifests command CLI command

$
0
0

General guide for the usage of import-puppet-manifests command can be found at import-puppet-manifests. Few other common issues and troubleshooting information related to import-puppet-manifests command are listed here as well.

 

Puppet module list command output format

For import-puppet-manifests command to work, 'puppet module list' command should print the module being imported in format <authorName>-<moduleName> (vX.X.X), where X.X.X is the version information. If the module being imported is not listed in this format when you use 'puppet module list' command, import-puppet-manifests command will not be able to import the puppet module as a service to application director.


A good example in the below sample output of 'puppet module list' command execution for which import-puppet-manifests command will work are nilesh-sample module and puppetlabs-apache module whereas it will fail to import mycustommodule as its not in format required by import-puppet-manifests command.


>> puppet module list

/Users/nilesh/.puppet/modules

├── nilesh-sample (v0.0.4)     // valid format as required by import command

├── puppetlabs-apache (v0.9.0) // valid format as required by import command

├── mycustommodule (???)       // invalid format and import command will not be import this module

 

To add author name and version information to your custom module you can create a metadata.json file under your module directory and update the name, version and other details as appropriate for your module. Once done, verify the output of the 'puppet module list' command to see if your module is being listed with above mentioned format.


Here is a sample metadata file which I created in my sample module directory:

{   "name": "nilesh-sample",   "version": "0.0.4",   "author": "Nilesh",   "source": "Module source information",   "summary": "One line description of the module",   "description": "Longer description of the module including an example",   "license": "The license the module is release under - generally GPLv2 or Apache",   "project_page": "The URL where the module source is located",   "dependencies": [],   "types": []
}

Viewing all articles
Browse latest Browse all 3135

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>