Story #83
closed
As a user I can install puppet modules using "puppet module install" and the v3 forge API
Status:
CLOSED - CURRENTRELEASE
Description
As a user I can install a module using the puppet module install command line using the v3 forge api enumerated at https://forgeapi.puppetlabs.com/
This will entail creating a new /v3/releases endpoint. We will have to go back to the pre-puppet 3.3 method of determining the repository and consumer as the ability to specify a context root has been disabled.
The api now requires pagination, offset tracking, and providing the urls for the next/previous queries in the case of pagination.
There are now many more options for filtering.
We will only have to support the /v3/releases endpoint at this time.
- Description updated (diff)
- Priority changed from Normal to High
- Sprint/Milestone set to 9
- Status changed from NEW to ASSIGNED
- Status changed from ASSIGNED to POST
- Platform Release set to master
- Status changed from POST to MODIFIED
- Platform Release changed from master to 2.7.0
- Status changed from MODIFIED to 5
- Groomed set to No
- Sprint Candidate set to No
This can be tested by using a fedora 22 system to install a puppet module using the standard puppet tooling. For example:
$ rpm -qa | grep puppet
puppet-4.1.0-1.fc22.noarch
$ pulp-admin puppet repo create --repo-id=forge --feed=http://forge.puppetlabs.com --queries torssh
...
$ pulp-admin puppet repo sync run --repo-id forge
...
$ puppet module install --module_repository http://.:forge@localhost tompurl/torssh
Notice: Preparing to install into /home/bcourt/.puppet/code/modules ...
Notice: Downloading from http://.:forge@localhost ...
Notice: Installing -- do not interrupt ...
/home/bcourt/.puppet/code/modules
└── tompurl-torssh (v0.1.0)
$
- Status changed from 5 to 6
Verified
[root@mgmt13 ~]# pulp-admin login -u admin -p admin
Successfully logged in. Session certificate will expire at Jul 28 16:28:55 2015
GMT.
[root@mgmt13 ~]# pulp-admin puppet repo create --repo-id=forge --feed=http://forge.puppetlabs.com --queries torssh
Successfully created repository [forge]
[root@mgmt13 ~]# pulp-admin puppet repo sync run --repo-id forge
+----------------------------------------------------------------------+
Synchronizing Repository [forge]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Downloading metadata...
[==================================================] 100%
Metadata Query: 1/1 items
... completed
Downloading new modules...
[==================================================] 100%
Module: 1/1 items
... completed
Task Succeeded
Publishing modules...
[==================================================] 100%
Module: 1/1 items
... completed
Generating repository metadata...
[-]
... completed
Publishing repository over HTTP...
... completed
Publishing repository over HTTPS...
... skipped
Task Succeeded
[root@mgmt13 ~]# puppet module install --module_repository http://.:forge@localhost tompurl/torssh
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from http://.:forge@localhost ...
Notice: Installing -- do not interrupt ...
/etc/puppet/modules
└── tompurl-torssh (v0.1.0)
- Status changed from 6 to CLOSED - CURRENTRELEASE
- Sprint set to January 2015
- Sprint/Milestone deleted (
9)
Also available in: Atom
PDF
.
Test whether puppet modules with extraneous files are properly uploaded.
This commit tests whether an upload of a puppet module containing extraneous files will be added to the pulp repo without any issues.
Refer Pulp.plan 1846 Closes #83