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 almost 3 years ago. Updated 12 months ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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

Duplicated by Puppet Support - Story #3548: r10k doesn't work with pulp_puppet CLOSED - DUPLICATE Actions

History

#1 Updated by etparton almost 3 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 almost 3 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 almost 3 years ago

  • Sprint Candidate changed from No to Yes

#4 Updated by mhrivnak almost 3 years ago

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

#5 Updated by mhrivnak almost 3 years ago

  • Sprint Candidate changed from Yes to No

#6 Updated by dalley 12 months ago

  • Duplicated by Story #3548: r10k doesn't work with pulp_puppet added

#7 Updated by dhollinger 12 months 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.

Please register to edit this issue

Also available in: Atom PDF