The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
PMT cannot install tarballs for modules that don't exist on the Forge
|Status:||Code Insufficient||Start date:||03/29/2012|
|Assignee:||Michal Ruzicka||% Done:|
|Affected Puppet version:||Branch:||https://github.com/puppetlabs/puppet/pull/1508|
|Keywords:||local-install, tarball, install, customer, pmtv3,|
At present, unless you specify the
--ignore-dependencies flag, the module tool behaves as follows when told to install a tarball:
- Verify that the name ends in
- Copy the tarball into the staging area
- Decompose the filename into author, module short name, and version components
- Ask the Forge for the dependency information for that author/module/version combination
- Download tarballs for each of the dependencies
- Unpack the tarballs as usual
If you try to install a tarball that doesn’t exist on the Forge, the tool fails.
If you try to install a tarball that doesn’t match the naming convention
authorname-modname-version.tar.gz, the tool fails.
If you try to install a tarball and you have no ability to connect to the forge, the tool fails.
If your tarball contains dependency information of its own, the tool ignores it.
#17 Updated by John Julien over 1 year ago
- Support Urls deleted (
eric sorenson wrote:
I’m untargeting this from 3.2.0 per discussions with Ryan and puppet devs yesterday.
Hey Eric,I know it was a while ago, but can you elaborate on the discussion you had with Ryan?
Are there future plans that obsolete this or is it just low priority?