Jira (PUP-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Andreas Wilke commented on PUP-6660 Re: cached catalogs setting not respected when --test is specified I'm using the puppet agent -t option at demos to show that the agent is still running with cached catalog when i updated my code with code manager and now i can control when the catalog will be updated. At command line it was easy to show that the agent is still using cached catalog. Now this option has gone and i need to tell them: Trust me, the agent is still using the cached catalog in the background . Would be great if we could have the option --use_cached_catalog. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6348) Puppet File server should support uploading/write files
Title: Message Title Andreas Wilke created an issue Puppet / PUP-6348 Puppet File server should support uploading/write files Issue Type: New Feature Assignee: Unassigned Created: 2016/05/24 12:56 AM Priority: Normal Reporter: Andreas Wilke customers using puppet orchestrator currently missing the feature to share files between nodes that will be created during a puppet orchestrator run. Example: creating a keytab on your kerberos server that needs to be shared with all your nodes inside a cluster after a puppet run on your kerberos server. The current workaround is to copy the keytab back to the master (for example using scp) within your catalog run to a mount point served by the puppet file server so it can be used by all systems triggered via orchestrator after the kerberos server. It would be nice if it is possible to use the custom file server mount points for uploads/writes as well and you can specify the upload of the file within puppet language so you no longer need to copy the file back with exec resources like scp. Add Comment
Jira (PUP-4290) Group type doesn't support description/comment field on Windows
Title: Message Title Andreas Wilke commented on PUP-4290 Re: Group type doesn't support description/comment field on Windows I got feedback from ING Poland that this missing description/comment field is the only reason why they are using the dsc_group resource inside our DSC module. But they are managing around 20 groups and they are seeing CPU spikes when using dsc_group because right now a PowerShell process is started each time a command is run. Rob Reynolds did already forward me the module ticket for this to get it fixed and only start one process for all dsc resources https://tickets.puppetlabs.com/browse/MODULES-2709. So if we add this functionality to the native group type it will help us to win ING DIB Poland as new customer. Maybe Steven Thwaites and Nicolas Corrarello can help us to check if KPN can send us the missing pull request if that helps? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5102) Define minimum version for a package
Title: Message Title Andreas Wilke assigned an issue to Kylo Ginsberg Puppet / PUP-5102 Define minimum version for a package Change By: Andreas Wilke Assignee: Andreas Wilke Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5102) Define minimum version for a package
Title: Message Title Andreas Wilke commented on PUP-5102 Re: Define minimum version for a package Kylo Ginsberg didn't know that versioning is such a complex topic and not all packages are using semver which makes it indeed hard to use it for all packages. But what if we implement this with a note to use it with caution that this should only be used for packages where version compare works fine? Why shouldn't we not support it? The customer reported it would really help him and could make his life easier to manage thousands of systems and hundreds of packages where it is almost impossible to get each node and each package installed to the same version level. This is a day to day battle for operations which doesn't always make sense to update productive systems only because there is a new version available. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5102) Define minimum version for a package
Title: Message Title
Andreas Wilke created an issue
Puppet / PUP-5102
Define minimum version for a package
Issue Type:
New Feature
Assignee:
Unassigned
Components:
Language
Created:
2015/08/28 7:33 AM
Priority:
Normal
Reporter:
Andreas Wilke
Customer Amadeus reported they would like to be able to define a minimal version for a package that should be installed so you can define the minimum version within a package. An example could be:
package { my package ensure = installed minversion = 1.3.0 }
So puppet will not install new releases of the package if there is already minimum version 1.3.0 installed. If installed package is older then defined version it should be updated.
Add Comment
