Project

Profile

Help

Story #1848

As a user I would like support for the `v3/modules` API endpoint, used by librarian-puppet.

Added by lastmikoi over 5 years ago. Updated over 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When using librarian-puppet(https://github.com/rodjek/librarian-puppet) with Puppet's V3 API in coordination with a pulp_puppet-powered forge, it is currently not possible for librarian-puppet to search for modules.

Indeed, librarian-puppet makes use of the `v3/modules` API endpoint, defined in https://forgeapi.puppet.com/#!/module.

From what I understood of the aforementioned API documentation, pulp_puppet would need to implement both module searching capability and specific module meta-data querying.

This story is closely related with https://pulp.plan.io/issues/1536, as it is basically the same story but for explicit librarian-puppet support instead of r10k.


Related issues

Has duplicate Puppet Support - Story #3548: r10k doesn't work with pulp_puppetCLOSED - DUPLICATE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by etparton over 5 years ago

This would be really useful, and not just for librarian-puppet support. New tools or new versions of existing tools might require the modules api to function, and supporting it would go a long way towards making sure that Pulp can support all tools that make use of the forge api.

#2 Updated by lastmikoi over 5 years ago

As discussed with bmbouter on IRC, here are more details about how to reproduce a testing environment for librarian-puppet:

  • Have an already-working pulp_puppet repository setup, published either through http or https, and containing the `puppetlabs-apache` module.
  • Install librarian-puppet
  • Create a `Puppetfile` file, containing:
#!/usr/bin/env ruby
#^syntax detection

forge "https://.:pulp_repo_id@pulp_hostname/"

mod 'puppetlabs-apache', "1.4.1"

(make sure to edit the 'forge' URI)

  • Run `librarian-puppet install --no-use-v1-api --verbose` in the same directory as the Puppetfile
  • Observe it being unable to find any module.

For the record, I am using ruby1.9.3p484, puppet 3.4.3 as well as librarian-puppet v2.2.1.

#3 Updated by bmbouter over 5 years ago

  • Sprint Candidate changed from No to Yes

#4 Updated by mhrivnak over 5 years ago

This could be handy during development: https://forgeapi.puppet.com/#interactive-demonstration

#5 Updated by mhrivnak over 5 years ago

  • Sprint Candidate changed from Yes to No

#6 Updated by dalley over 3 years ago

  • Has duplicate Story #3548: r10k doesn't work with pulp_puppet added

#7 Updated by dhollinger over 3 years ago

This change is also needed by Puppet's r10k code management tool and Puppet Enterprise's Code Manager tool. Both tools require the /modules endpoint in addition to the /releases endpoint to deploy Puppet Modules from a Pulp repository.

Additionally, librarian-puppet was migrated from rodjek to Vox Pupuli some time ago as well. Project URL - https://github.com/voxpupuli/librarian-puppet.

#8 Updated by bmbouter over 2 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

#9 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF