[PDB-1035] Our module won't work with PDB 3.0.0 once released, as it has a new module package name Created: 2014/11/17  Updated: 2015/07/10  Resolved: 2015/06/04

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: PDB module-4.1.0
Fix Version/s: PDB module-5.0.0, PDB 3.0.0

Type: Bug Priority: Normal
Reporter: Ken Barber Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by PDB-663 Convert packaging to use ezbake Closed
Template:
Epic Link: PDB Version 3 Retirements
Story Points: 1
Sprint: PuppetDB 2015-01-28, PuppetDB 2015-06-03, PuppetDB 2015-06-17

 Description   

In PuppetDB 3.0.0 the terminus package name is now `puppetdb-termini` but our module still uses the old standard. Need to figure out what to do here. The override is to use `terminus_package` parameter in one of the classes, but this seems less optimal for long term use.
This ticket also includes setting the defaults for PDB 3.0.0, such as the test_url to the new `/pdb/meta/v1/version` endpoint.



 Comments   
Comment by AJ Roetker [ 2015/01/21 ]

Would it make sense to do a major release of the module as well corresponding to the major for the service? There's a module PR open right now (for masterless setups) that would also do better with some refactors that would be better in a major as well... thoughts Ken Barber?

Comment by Ken Barber [ 2015/02/03 ]

Old PR was here: https://github.com/puppetlabs/puppetlabs-puppetdb/pull/165

Comment by Ryan Senior [ 2015/05/12 ]

Baking in some time to pair on this and spread some knowledge.

Generated at Fri Oct 18 01:20:11 PDT 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.