Ticket #1096 (accepted defect)

Opened 11 years ago

Last modified 10 years ago

bcfg2-info mappings broken for Package entries

Reported by: solj Owned by: solj
Priority: major Milestone: Bcfg2 1.3.5 Release (Bugfix)
Component: bcfg2-server Version: 1.0
Keywords: Cc:

Description (last modified by solj) (diff)

On a machine with Packages properly configured and working...

> mappings Package
 Plugin  | Type  | Name  


Change History

comment:1 Changed 11 years ago by solj

  • Owner changed from desai to solj
  • Status changed from new to accepted
  • Description modified (diff)

comment:2 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.2 Release (Bugfix) to Bcfg2 1.2.3 Release (Bugfix)

Moving to 1.2.3

comment:3 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.3 Release (Bugfix) to Bcfg2 1.3.0 Release

Moving to 1.3

comment:4 Changed 11 years ago by

I'm not sure this is reasonable (or maybe even possible) due to the way mappings is implemented. It looks through each generator for its inventory as recorded in plugin.Entries. For plugins like Packages that don't store their entries in Entries (but rather use HandlesEntry/HandleEntry? to do the "slow" lookup) this kind of inventory just isn't kept.

So we have a few options:

  1. Keep mappings as-is and acknowledge that more "dynamic" plugins simply aren't going to work;
  1. Do an inventory of entries in Bundler and iterate over those rather than over the generators, and acknowledge that entries in templated bundles simply aren't going to work;
  1. Some kind of hairy hybrid of those two approaches (which would likely mean doing both and taking a union of the results).

comment:5 Changed 10 years ago by solj

  • Milestone changed from Bcfg2 1.3.0 Release to Bcfg2 1.3.2 Release (Bugfix)

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as accepted

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.