date:20160330

Jira (PUP-6091) Lookup CLI should use unquoted dot in key as sub-lookup

2016-03-30 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6091 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Lookup CLI should use unquoted dot in key as sub-lookup  
 
 
 
 
 
 
 
 
 
 
It sounds like you're in support of my proposal then. I think the access function deserves a separate JIRA given that it is a generic Puppet function with no impact on how lookup parses its keys. 
As mentioned, supporting dotted notation everywhere is a breaking change for users that rely on the current lookup behavior. They will now need to quote dotted keys used outside of the interpolation. How do we handle that? Is it enough with a documentation change and a release note? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-6100) Question / Feature Request: Make value of "configuration version" visible to puppet manifests

2016-03-30 Thread Johnson Earls (JIRA)

Title: Message Title

Johnson Earls commented on PUP-6100

Re: Question / Feature Request: Make value of "configuration version" visible to puppet manifests

Eric Sorenson, Henrik Lindberg: The problem I'm trying to solve is this:
I've got an existing system file which Puppet does not control, but the content of which is partially managed by Puppet. Right now, I'm doing this using augeas to add or remove specific entries as specified through my defined resource type.
However, I would also like to provide an option to "purge" all entries in that file that were created at some point by puppet, but were not managed during the current run.
My first attempt was just to purge entries first, then let the entries get added back in. But this causes an unacceptable period of time during which those entries do not exist. The proper solution would be to create some puppet code that is ordered after all instances of the defined resource type, and purges any entries that were not invoked during this run.
However, there's no way to do that within the puppet language – no way for puppet code to query the resources after the fact and find out what resources were declared during the run ; no way for the resources themselves to "accumulate" a list of the resource ; generally no way for puppet code to know "this resource was declared with this name".
The solution I was aiming for, once I saw the "configuration version", was to use that value as part of the "managed by puppet" comment that gets added to each entry. The purge code could then just remove any entry which has the "managed by puppet" comment but has a different configuration version.
This is not pretty (since it rewrites those entries every time puppet runs), but would prevent the wholesale remove-and-re-create of puppet-managed entries within the file.
I hope this makes sense.
– Johnson

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PDB-2124) Please support some database besides PostgresQL

2016-03-30 Thread Johnson Earls (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Johnson Earls commented on  PDB-2124 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Please support some database besides PostgresQL  
 
 
 
 
 
 
 
 
 
 
Since PostgreSQL is still taboo (I think the real reason is that it's a competing product, and not any real security issue), I'm coming back to this with a different tack: 
Is there any documentation on how to extend puppet with a new backend/plugin for storeconfigs_backend or facts_terminus - some way that I can at least have puppet record somewhere each time an agent runs, and what facts were used for that agent run? I thought I could use the puppet reports for this, but the puppet reports do not include the facts. 
Thanks, – Johnson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

98 matches

Mail list logo