Locally Written Puppet Module Does Not Dislay Version Number With: puppet module list

[Allen Santora]

Greetings,

(puppet-server-3.5.1 on CentOS 6.4)

I'm writing my own nodejs manager in Puppet and I want to enforce a version number

I have generated the module skeleton with the command: # puppet module generate company-nodejs
in /etc/puppet/modules

I then created /etc/puppet/modules/company-nodejs/metadata,json with the
basic content found at the URL:

https://docs.puppetlabs.com/puppet/latest/reference/modules_publishing.html#write-a-metadatajson-file

(... with appropriate local edits to metadata.json including...

"version": "0.0.1",

)

I then check the module with the command below but I am not getting a version number

#  puppet module list | grep node

company-nodejs (???)

Does anyone know why I am not getting a version number?

Thanks in advance.

[Nikola Petrov]

Try changing the Mdoulfile instread of the metadata file.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3655002c-3caf-49f6-8ef2-491cad1f88ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Antoine Cotten]

What nikolavp said is true, the metadata.json became the standard starting from Puppet 3.6, but since you use 3.5 the Modulefile still prevails.

Off subject: any reason not to upgrade your master? I have really bad memories of Puppet 3.5 on CentOS, whereas 3.6 fixed all my troubles. Would also allow you to use your metadata.json files as you intended.

Cheers,

Toni