Custom Query (894 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (61 - 63 of 894)

Ticket Owner Reporter Resolution Summary
#1092 https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc fixed Add more convenient convenience methods for Properties
Description
(06:17:40 AM) tie: ok, working with properties is way too clumsy
(06:18:00 AM) tie: to get the FQDN property corresponding to the current host in a template, I need to do:
(06:18:12 AM) tie: ${[el.text for el in metadata.Properties['props.xml'].Match(metadata) if el.tag=='FQDN'][0]}
(06:20:27 AM) tie: ideally, this should be more like ${ metadata.MyProperties['props.xml'].FQDN[0].text}
(07:40:48 AM) stpierre: tie: how would you feel about ${metadata.Properties['props.xml'].get("FQDN").text} or ${metadata.Properties['props.xml'].get_all("FQDN")[0].text} ?
(07:44:04 AM) stpierre: i guess it would have to be ${metadata.Properties['props.xml'].get("FQDN", metadata=metadata).text} or something similar
(07:44:23 AM) stpierre: making that a kwarg doesn't make sense, so just get("FQDN", metadata).
(07:58:54 AM) tie: stpierre: ${metadata.Properties['props.xml'].get("FQDN").text} is OK, definitely much better than the current situation, though I'm not sure how it would handle multiple FQDN tags
(07:59:24 AM) tie: passing the metadata to a member of the metadata object seems superfluous
(08:00:29 AM) tie: it is very nice to have the entire set of Properties accessible, but there should be a shortcut that leads to the Properties of the current client or group
(08:01:30 AM) stpierre: you'd handle multiple tags with get_all.
(08:01:50 AM) stpierre: given the way connectors work we may not be able to eliminate the "extra" metadata argument.  i'll look into that
(08:01:50 AM) tie: ah, I see what you meant
(08:02:38 AM) tie: may I suggest adding an object member which links to the parent?
(08:03:03 AM) tie: e.g. whenever metadata gets Properties added, it does: self.properties.parent = self
(08:03:32 AM) tie: so you can get a link to the current metadata inside the Properties object
(08:03:58 AM) tie: then it is trivial to add: if metadata == None: metadata == self.parent
(08:04:32 AM) stpierre: that would have to change the connector plugin interface as a whole
(08:04:43 AM) stpierre: it's not that this is impossible, it may just be improbable for a bugfix release :)
(08:07:15 AM) stpierre: made particularly difficult by the fact that metadata.Properties is not a Properties plugin object (or similar), but a dict().
(08:08:08 AM) tie: it can be subclassed, so it would retain all dict properties
(08:08:46 AM) stpierre: i know -- like i said, not impossible, just improbable for 1.2.1
#1091 https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc solj fixed Add back toggle_debug functionality to Packages
Description

As per http://docs.bcfg2.org/server/plugins/generators/packages.html#using-bcfg2-server. This is really useful when you need to determine which package is pulling in a particular dependency.

#1090 desai m4z <[email protected]…> duplicate bcfg2-admin pull option to keep info files.
Description

When I do a "bcfg2-admin pull" from somewhere, and an "info.xml" or ":info" (and maybe "info", don't use those) already exists for that file, the info file is overwritten with whatever the client has.

Especially in the case of a host-specific pull, this is not what I'd expect. It would be nice for bcfg2-admin to support a knob to keep the info file as-is (or even to make this the default behavior).

Note: See TracQuery for help on using queries.