Jira (PUP-10052) Move indirector global config setting out of the default hooks
Title: Message Title Justin Stoller commented on PUP-10052 Re: Move indirector global config setting out of the default hooks After this ticket was created we audited the settings for threadsafety and the storeconfigs setting is not one we have found any uses of setting at runtime. It therefore didn't go into our general threadsafe settings work (unlike tasks, strict, strict_variables...). As such, when the hook is currently called (during initialization) is fine even in a multithreaded environment and re-setting this to another value during runtime (eg catalog compilation) won't be supported, consequently the fact that the hook isn't threadsafe shouldn't be a problem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326773.1569514905000.4025.1580257740107%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Melissa Stone commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax This has passed ci as a part of puppet-agent 5.5.18.44.g1c1c714b Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.3880.1580252760344%40Atlassian.JIRA.
Jira (PUP-10173) Set CI jobs to run only 'high' risk acceptance tests
Title: Message Title Melissa Stone commented on PUP-10173 Re: Set CI jobs to run only 'high' risk acceptance tests I'm going to go ahead and resolve this. CI looks stable and this has been in for a week now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339228.1576177064000.3865.1580252580339%40Atlassian.JIRA.
Jira (PUP-3721) Puppet resource should always emit the provider
Title: Message Title Melissa Stone commented on PUP-3721 Re: Puppet resource should always emit the provider passed ci as a part of puppet-agent 6.12.0.140.g98760fed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.60191.1417547005000.3855.1580252460227%40Atlassian.JIRA.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Ben Ford commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax John Bollinger, no. Sorry I wasn't more clear. What I want is for collectors to not implicitly realize, just the same as you do. More specifically, I want collectors to do exactly one thing – just collect resources into a thing that you can do something with. If you want to add relationships, then yes, you can add relationships to a collection. If you want to realize, then yes, you can realize a collection. But simply invoking the collector shouldn't do anything other than collect. That would be a bigger breaking change, since so much current code relies on the side effect, but that's what I'd like long term. I'd also like a better query language, since there's currently not a way to collect "all packages except for those tagged as puppet_enterprise". The manifold type is simply a bandaid to separate the relationship case from the realize case without drastic language changes today. It can also be used on older Puppet versions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.191187.1494891335000.3615.1580247661655%40Atlassian.JIRA.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title John Bollinger commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax The issue is when using Puppet Enterprise for example there are packages that are virtual and depending upon how you use collectors this will cause some nasty behavior That's certainly an issue, Chris Denneen, but the issue we're discussing here is broader. How does one propose to continue to use Collectors (or PQL) to allow for the desired behavior that Yum gets updated before yumrepo which are all applied before all other packages. With current PE alone, one would need to write a more selective collector. Either additional resource titles could be excluded specifically, or perhaps tags could be brought to bear to exclude the Puppet Enterprise packages. If one is willing to engage third-party modules, then it looks like Ben's Manifold module can stand in for a collector in that particular case and many similar ones. As I already commented, the broader issue revolves around the fact that collectors serve dual purposes. Way back in Puppet 2, they served only to realize virtual resources and collect exported ones. They retain those functions today, but since P3 they also serve to group resources as operands for the chain operators and for parameter overrides. Presently, there is no way to obtain either of the latter two collector behaviors without the first, but there could be in Puppet 8 (or maybe even in Puppet 7?). I already suggested one way that could be implemented, but there are certainly others, including alternatives along the lines of Ben's module. The first iteration of this discussion established that there was still strong support for exported and virtual resources at that time. Perhaps that has since waned, but I, at least, still want to keep them. On the other hand, the specifics of current collector syntax and semantics are much more open to consideration, and from my perspective, that's where PQL, Datalog, Manifold, etc. could come into the picture. Some of those can already be used to address parts of the problem. Maybe PE should avoid the use of Virtual Resources? But what's to stop Datadog, Sensu, etc vendors from doing the same. Whether PE or anyone else should stop using virtual resources is a separate question. The specific problem Ben brought up would no longer manifest if PE did so, but that would not address the larger issue.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Chris Denneen commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax The issue is when using Puppet Enterprise for example there are packages that are virtual and depending upon how you use collectors this will cause some nasty behavior: Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-postgresql-pglogical]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-postgresql-pgrepack]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-java-devel]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-activemq]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-razor-libs]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-razor-server]/ensure: current_value 'purged', should be 'latest' (noop) Notice: Class[Puppet_enterprise::Packages]: Would have triggered 'refresh' from 6 events This is caused by the above example (to make sure Package['yum'] -> Yumrepo<| |> -> Package<| |>) Yumrepo<| |>->Package<| title != 'yum' |> How does one propose to continue to use Collectors (or PQL) to allow for the desired behavior that Yum gets updated before yumrepo which are all applied before all other packages. (Reason Yum has to be updated first is because sometimes features being added to yumrepos ssl, parameters, etc won't work with old versions of yum so the package must be applied first) but you want the yumrepos to be applied before all other packages are attempted to be installed/upgraded. Maybe PE should avoid the use of Virtual Resources? But what's to stop Datadog, Sensu, etc vendors from doing the same. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title
Henrik Lindberg commented on PUP-10259
Re: Hiera cannot interpolate non-string values
To be honest I am so sick and tired of the horrible hiera interpolation syntax - here with interpolation functions that makes the result not be an interpolation - I think it is just bizarre ... I never liked this because playing tricks with interpolation functions is pretty much the only thing that can be done and retaining backwards data compatibility. Using lookup_options is however different in that there we decide the meaning/encoding of whatever is described there. So, we could "type" the meaning of a key - for example "get the value using getvar()" (which the example above from thomas means). Now, if we instead generalize that to state that the looked up value is given to a mentioned function before being returned - the lookup would first produce 'facts.selinux.enabled', and the lookup_option would say that it should be passed through getvar(), and thus yielding the result of getvar('facts.selinux.enabled'). This mechanism can then be used such that if the called function accepts a LookupContext then it would be given it when function is called - the called function can then also perform a "not-found" as an outcome, and it would be able to (somehow) also keep track of that context for recursion. (This is something I did in a Puppet language hiera 5 backend function - where you would simply write "getvar('facts.selinux.enabled') as the value for the key. The code for that ppyaml backend function is here: https://github.com/hlindberg/tahu/blob/master/lib/puppet/functions/tahu/ppyaml_key.rb in case someone is interested.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Thomas Hallgren commented on PUP-8593 Re: Add alias to lookup_options and make it redirect to lookup of the alias Not sure why that is. The only thing that the current alias doesn't, is to propagate the "not-found" condition. It preserves the type and it guards against recursion. Perhaps I'm missing something but besides the "advanced features" (which I personally think we should avoid), I don't see more value added here. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242722.1521802594000.3263.1580239260216%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Thomas Hallgren commented on PUP-10251 Re: Feature request: Add a way to turn looked up undef values in Hiera into "not found" Yes, of course. I meant "not-found", not undef. Doh! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343178.1579803772000.3254.1580238840543%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Henrik Lindberg commented on PUP-10251 Re: Feature request: Add a way to turn looked up undef values in Hiera into "not found" Thomas Hallgren I thought strict_alias would result in a "not-found" and that was the entire idea why having it in the first place. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343178.1579803772000.3243.1580238540248%40Atlassian.JIRA.
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Henrik Lindberg commented on PUP-8593 Re: Add alias to lookup_options and make it redirect to lookup of the alias Thomas Hallgren That is solving PUP-8341, a completely different problem than this ticket (what is described above would also benefit from having some kind of "strict" option). I think PUP-8341 should be reopened for the purpose of adding strict_alias interpolation function. This ticket is about having a more powerful mechanism for aliasing than what is currently possible with the hiera interpolation functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242722.1521802594000.3237.1580238240107%40Atlassian.JIRA.
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title Trevor Vaughan commented on PUP-10259 Re: Hiera cannot interpolate non-string values Thomas Hallgren Seems reasonable to me. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.3211.1580237880452%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Henrik Lindberg commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation Nick Walker, I think that makes more sense as well - then there is just an entry barrier that is checked before compiling - I suppose that means "go over there instead" - or is that switch over to another version done based on something else? To me it seems that a compiling server would be able to keep track of the number of compiles per version that it has ongoing (there are all active in memory, so if it dies they cannot be ongoing). If there are multiple servers acting on the same information it gets more complicated. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343770.1580166495000.3193.1580237640323%40Atlassian.JIRA.
Jira (PUP-10259) Hiera cannot interpolate non-string values
Title: Message Title Thomas Hallgren moved an issue Puppet / PUP-10259 Hiera cannot interpolate non-string values Change By: Thomas Hallgren Key: HI PUP - 599 10259 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.3177.1580237340575%40Atlassian.JIRA.
Jira (HI-599) Hiera cannot interpolate non-string values
Title: Message Title
Thomas Hallgren commented on HI-599
Re: Hiera cannot interpolate non-string values
Perhaps we should have something identical to the strict_alias proposed in PUP-8593?. Given that an interpolation without any function is identical to scope, we could make strict imply a strict lookup in scope. E.g.
docker::selinux_enabled: "%{strict('facts.selinux.enabled')}"
would give the desired result.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.244421.1522942982000.3157.1580237280323%40Atlassian.JIRA.
Jira (PUP-10251) Feature request: Add a way to turn looked up undef values in Hiera into "not found"
Title: Message Title Thomas Hallgren commented on PUP-10251 Re: Feature request: Add a way to turn looked up undef values in Hiera into "not found" Henriks example results in an empty string. The strict_alias proposed in PUP-8593 would result in an undef. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343178.1579803772000.3148.1580236920223%40Atlassian.JIRA.
Jira (PDB-4637) Lock out the puppetdb data user during migration
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4637 Lock out the puppetdb data user during migration Change By: Austin Blatt Team: HA Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343744.1580162942000.3137.1580236800551%40Atlassian.JIRA.
Jira (PDB-4639) Add connection init check to Hikari pools
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4639 Add connection init check to Hikari pools Change By: Austin Blatt Team: HA Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343754.1580164659000.3135.1580236800463%40Atlassian.JIRA.
Jira (PDB-4638) Move migrations into a single transaction
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4638 Move migrations into a single transaction Change By: Austin Blatt Team: HA Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343751.1580164488000.3142.1580236800772%40Atlassian.JIRA.
Jira (PDB-4636) Add configration option migrate
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4636 Add configration option migrate Change By: Austin Blatt Team: HA Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343741.1580162292000.3132.1580236800410%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Molly Waggett commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation Just because a new version has been deployed doesn't necessarily mean that older versions aren't still in use, like if you do a bunch of deploys in a short period of time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343770.1580166495000.3127.1580236560295%40Atlassian.JIRA.
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Thomas Hallgren commented on PUP-8593 Re: Add alias to lookup_options and make it redirect to lookup of the alias A simpler, and perhaps more straight forward solution that was proposed in PUP-8341, is to introduce an additional interpolation function. This has already been done in the Go version of Hiera. The function is called `strict_alias` and behaves like `alias` with the exception that a not found is propagated instead of translated into an empty string. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.242722.1521802594000.3121.1580236440635%40Atlassian.JIRA.
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title David Kramer assigned an issue to Sean McDonald Puppet / PUP-8318 Allow client tools and classifier gem to support parameters Change By: David Kramer Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229070.1515102987000.3077.1580235480183%40Atlassian.JIRA.
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title David Kramer updated an issue Puppet / PUP-8318 Allow client tools and classifier gem to support parameters Change By: David Kramer Team: Dumpling Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229070.1515102987000.3073.1580235420217%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Nick Walker commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation I don't quite understand this proposal. Would it make sense to instead write a timestamp to the n-1 version of code when the n version of code is being deployed? So basically you write a timestamp indicating when the code was superseded as opposed to writing a timestamp at the beginning of every compile? I'd imagine the ideal state is you write down metadata on all the compiles that are currently happening at the time you deploy new code and then during a garbage collection process later you just confirm the compiles that were happening at the time you deployed the new code are no longer running. My guess would be we don't have a way to know the compiles that were running or a way to confirm they are no longer running? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343770.1580166495000.2939.1580233200831%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Molly Waggett commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation Whatever start time we record, I think the idea was to not purge unless some (yet-to-be-determined) amount of time has passed, where we're confident the compile would be finished. We considered recording when the compile has finished, but that definitely creates a race condition if we do the check while a compile is in progress and hasn't recorded its end time yet. But I think you're right that we didn't consider the case where we do the time check and then a compile starts before the code dir is actually purged.. We did decide that we'd always keep version n-1, where version n is the most recent for a given environment, in the hopes that this would minimize the chance that we'd purge a version that was still being used. Does that seem sane to you? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343770.1580166495000.2896.1580232240155%40Atlassian.JIRA.
Jira (PUP-10248) windows pidlock can raise access denied
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10248 windows pidlock can raise access denied Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343144.1579760192000.2782.1580228460395%40Atlassian.JIRA.
Jira (PUP-10258) Register and Start Puppet Agent as protected service
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10258 Register and Start Puppet Agent as protected service Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343855.1580216378000.2760.1580228101012%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Mihai Buzgau Sprint: PR - Triage Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342859.1579626792000.2748.1580228040459%40Atlassian.JIRA.
Jira (FACT-2306) Add support for AWS IMDSv2
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2306 Add support for AWS IMDSv2 Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342859.1579626792000.2746.1580228040371%40Atlassian.JIRA.
Jira (PUP-10257) Write timestamp to file in environment when beginning compilation
Title: Message Title Henrik Lindberg commented on PUP-10257 Re: Write timestamp to file in environment when beginning compilation Would this not then create a problem with not knowing if that compile has finished, and would this not also create a race condition (just after checking a compilation starts). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343770.1580166495000.2739.1580227560103%40Atlassian.JIRA.
Jira (PUP-10258) Register and Start Puppet Agent as protected service
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10258 Register and Start Puppet Agent as protected service Change By: Gheorghe Popescu Acceptance Criteria: Puppet can be registered to the ELAM driver can be started as protected service. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343855.1580216378000.2615.1580218800127%40Atlassian.JIRA.
Jira (PUP-10258) Register and Start Puppet Agent as protected service
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-10258 Register and Start Puppet Agent as protected service Issue Type: Task Assignee: Unassigned Created: 2020/01/28 4:59 AM Priority: Normal Reporter: Gheorghe Popescu Currently the service creation is handled in: https://github.com/puppetlabs/puppet/blob/master/ext/windows/service/daemon.rb Puppet service must be registered with the system before it can be started as protected: https://docs.microsoft.com/en-us/windows/win32/services/protecting-anti-malware-services-#registering-the-service-without-rebooting-the-system Starting the service as protected: Call the CreateService API to create a service object and add it to the service control manager (SCM) database. Call the SetServiceObjectSecurity API to set the security descriptor of the service object created in step 1. Call the ChangeServiceConfig2 API to mark the service as protected, specifying the new SERVICE_CONFIG_LAUNCH_PROTECTED enumeration value, which has been added in Winsvc.h (as of Windows 8.1). https://docs.microsoft.com/en-us/windows/win32/services/protecting-anti-malware-services-#starting-the-service-as-protected
Jira (FACT-2308) Fix Facter.add
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2308 Fix Facter.add Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343849.1580215168000.2608.1580215560055%40Atlassian.JIRA.
Jira (FACT-2308) Fix Facter.add
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2308 Fix Facter.add Issue Type: Task Assignee: Unassigned Created: 2020/01/28 4:39 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (PUP-9943) User type has custom retrieve() with non-standard return values
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-9943 User type has custom retrieve() with non-standard return values Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320115.1565272699000.2602.1580215140236%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Gheorghe Popescu Release Notes Summary: If the first Puppet Agent run was is done under SYSTEM account, following runs done by Administrator users were failing to send the report to master due to insufficient file permissions caused by the implementation of `Puppet::Util.replace_file`.Puppet now uses the new `Puppet::FileSystem.replace_file` method which correctly handles files permissions on Windows. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.2550.1580208540679%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Gheorghe Popescu Release Notes Summary: If the first Puppet Agent run was done under SYSTEM account, following runs done by Administrator users were failing to send the report to master due to insufficient file permissions caused by the implementation of `Puppet::Util . replace_file`. Changed puppet to use Puppet now uses the new `Puppet::FileSystem.replace_file` method which correctly handles files permissionson Windows. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.2532.1580208480319%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Gheorghe Popescu Release Notes Summary: If the first Puppet Agent run was done under SYSTEM account, following runs done by Administrator users were failing to send the report to master.Changed puppet to use `Puppet::FileSystem.replace_file` which correctly handles files permissions Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.2521.1580208420584%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Gheorghe Popescu Release Notes Summary: If the first Puppet Agent run was done under SYSTEM account, following runs done by Administrator users were failing to send the report to master.Changed puppet to use Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.2515.1580208360676%40Atlassian.JIRA.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: Gheorghe Popescu Release Notes Summary: TBD - Will provide these If the first Puppet Agent run was done under SYSTEM account, following Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.2501.1580208240648%40Atlassian.JIRA.
Jira (FACT-2307) Add ability to cache external facts
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2307 Add ability to cache external facts Change By: Ciprian Badescu Sprint: NW - 2020-02-05 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343836.158020703.2467.1580207220222%40Atlassian.JIRA.
Jira (FACT-2307) Add ability to cache external facts
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2307 Add ability to cache external facts Change By: Ciprian Badescu Currently only * list-cache-groups should list the external facts files * external resolvers should provide a list of resolved facts, to be used in current caching mechanism (eg. instead of core directly calling facts is supported . Since this is done based on resolvers add_external_fact , but a proxy resolver method that will cache the facts names, etc.) * cache module should handle both internal process for caching and external facts might look quite different resolvers (eg . This ticket is intended to track the investigation instead of what work would relying on directly receiving name()/names() instead from resolver they could be needed to allow the caching of external facts by received as arguments *or* implement name /names in external resolvers , analogous to the UX of caching by group name for core facts etc . That work also includes updating the command line option which lists cachable facts to include ) * if same external facts . file is present in more than one place, throw a warning and use only one of them, because filename is used as key for caching and must be unique Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2307) Add ability to cache external facts
Title: Message Title Ciprian Badescu assigned an issue to Unassigned Facter / FACT-2307 Add ability to cache external facts Change By: Ciprian Badescu Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.343836.158020703.2462.1580207160542%40Atlassian.JIRA.
Jira (FACT-2307) Add ability to cache external facts
Title: Message Title Eric Sorenson created an issue Facter / FACT-2307 Add ability to cache external facts Issue Type: Task Assignee: Ciprian Badescu Created: 2020/01/28 2:23 AM Labels: cache Priority: Normal Reporter: Eric Sorenson Currently only caching of core facts is supported. Since this is done based on resolvers, the internal process for caching external facts might look quite different. This ticket is intended to track the investigation of what work would be needed to allow the caching of external facts by name, analogous to the UX of caching by group name for core facts. That work also includes updating the command line option which lists cachable facts to include external facts. Add Comment
Jira (FACT-1472) Ensure the collection has enough information about external facts to cache them.
Title: Message Title Ciprian Badescu commented on FACT-1472 Re: Ensure the collection has enough information about external facts to cache them. Following analysis, the following tasks are needed: refactor external facts implementation to create a list of external facts files and associated resolvers and solve them in one step implement caching of external facts: list-cache-groups should list the external facts files external resolvers should provide a list of resolved facts, to be used in caching (eg. instead of directly calling facts.add_external_fact, but a proxy resolver method that will cache the facts names, etc.) cache module should handle both internal and external resolvers (eg. instead of relying on directly receiving name()/names() instead from resolver they could be received as arguments or implement name/names in external resolvers, etc.) if same external facts file is present in more than one place, throw a warning and use only one of them, as filename is used as key for caching and must be unique Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10218) Puppet incorrectly detecting stale pidfile
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10218 Puppet incorrectly detecting stale pidfile Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.341249.1578386676000.2375.1580200140359%40Atlassian.JIRA.
