Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Beth, > Thanks for the query. We're tracking the interest from our customers > (both OSP and enterprise) to gauge whether we prioritize adding Rocky > Linux to our test matrices for various reasons, an example being > supported modules.   Sure testing the modules make sense, similar to how you

Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Peter, Thanks for the query. We're tracking the interest from our customers (both OSP and enterprise) to gauge whether we prioritize adding Rocky Linux to our test matrices for various reasons, an example being supported modules. Have a great weekend, Beth On Fri, May 14, 2021 at 12:10 PM Pe

Re: [Puppet-dev] Re: Support for CentOS Stream 9

Hi Beth, > I added a CentOS Stream 9 card to our Puppet Idea Portal >  under the Puppet Core tab, the > Idea Portal is how Product tracks feedback/feature requests for the > various products in our portfolio. Thanks for your input! Thank you for adding it.

[Puppet-dev] Re: Support for CentOS Stream 9

Hi Pete, I added a CentOS Stream 9 card to our Puppet Idea Portal under the Puppet Core tab, the Idea Portal is how Product tracks feedback/feature requests for the various products in our portfolio. Thanks for your input! Beth On Tuesday, May 11, 2021

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

Hi Josh, > All resolved issues should be available in nightly puppet7 builds, such > as http://nightlies.puppet.com/yum/puppet7-nightly-release-el-8.noarch.rpm > . > It'd be great to get confirmation in the next few days that

Re: [Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

Thanks Pete for putting this together! Some comments below: On Wed, Dec 2, 2020 at 12:33 AM Peter Meier wrote: > Hi All, > > > Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' > > repos to point to the new 'puppet7' release from a couple of weeks ago. > > If you're already

[Puppet-dev] Re: [Puppet Users] Upcoming changes to the rolling 'puppet' repos!

Hi All, > Tomorrow morning (~9am Pacific) we'll be updating the rolling 'puppet' > repos to point to the new 'puppet7' release from a couple of weeks ago. > If you're already using the 'puppet' release packages (such > as http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm >

[Puppet-dev] Re: [Puppet Users] Issue with puppet6 release packages

Hi Peter, Due to some issues with the rollout of the repos yesterday, we're going to leave the rolling 'puppet' repo pointing at puppet6 until at least November 30th so we don't cause unexpected upgrades for folks while we have many people out for US holidays. On Fri, Nov 20, 2020 at 12:58 PM Pet

[Puppet-dev] Re: [Puppet Users] Issue with puppet6 release packages

> * If /etc/yum.repos.d/puppet.repo exists -- you are affected. Unless > you want to be subscribed to the repo with rolling updates, you > should uninstall and reinstall the release package. > * If /etc/yum.repos.d/puppet6.repo exists -- you are not affected. So what is the intend for

[Puppet-dev] Re: Puppet Platform 6.19.0 is now available

Hello, During our effort to remove the harmful terminologies from Puppet, we’ve introduced the following regression: https://tickets.puppetlabs.com/browse/PUP-10722 We’re currently working on providing a new release (6.19.1) that contains a fix. Please refrain from upgrading to the la

[Puppet-dev] Re: PDK 1.16.0 now available

[sad trombone] It turns out the macOS package manager doesn't update the permissions of existing files if that is the only change, so if you have previously installed the broken package (1.16.0.1) you will need to completely uninstall the old package before installing the fixed package (1.16.0.2).

[Puppet-dev] Re: PDK 1.16.0 now available

On macOS, there was a permissions issue in the PDK 1.16.0 packages (released as PDK 1.16.0.1) which prevented most PDK commands from executing. PDK 1.16.0.2, a new release that addresses the permissions issue, is now available. This release contains no other changes. We're sorry for the inconveni

[Puppet-dev] Re: Removing puppet-client-tools from puppet6

Hi Matt, The puppet-client-tools package has been replaced by the puppetdb_cli gem. You can find installation instructions in the PuppetDB docs . If you encounter any issues using the gem please submit a PDB ticket on Jira, or find m

[Puppet-dev] Re: Removing puppet-client-tools from puppet6

Might one inquire as to what you consider "soon"? On Thursday, April 4, 2019 at 6:17:47 PM UTC-4, Molly Waggett wrote: > > Hey folks! > > Unfortunately we've had to pull the puppet-client-tools packages from the > puppet6 package repositories. These packages were built against puppet5 and > are

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 6.4.2

This release has been renumbered to* 6.4.3*, the release with the original number was shipped on April 30. There is no change in timeline for this release, the dates below still apply. Timeline Stop Ship Line milestones targeted for July 9 (puppet-agent) and July 10 (PuppetDB and Puppet Serve

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 6.0.9

This release has been renumbered to* 6.0.10*, the release with the original number was shipped on April 30. There is no change in timeline for this release, the dates below still apply. Timeline Stop Ship Line milestones targeted for July 5 (puppet-agent) and July 8 (PuppetDB and Puppet Serve

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 5.5.14

This release has been renumbered to 5.5.15, the release with the original number was shipped on April 30. There is no change in timeline for this release, the dates below still apply. Timeline Stop Ship Line milestones targeted for July 2 (puppet-agent) and July 3 (PuppetDB and Puppet Server)

[Puppet-dev] Re: [ACTION] Changes to release package links

Hi all, We have enabled repositories on release-archives.puppet.com. If you're using Puppet 3, install the puppet-archives-release-* packages. If you're using Puppet 4, install the puppetlabs-release-pc1-* packages. We do not yet have a timeline for when these packages will be re-archived from t

[Puppet-dev] Re: [ACTION] Changes to release package links

Hi all, As you may have seen, the packages we removed from {yum,apt}.puppetlabs.com this week have been put back. This was due to an outage and the need to restore from backups. While we originally did not intend to enable repositories on release-archives.puppet.com, the overwhelming demand has m

[Puppet-dev] Re: [ACTION] Changes to release package links

Hey folks, REMINDER that the repository path changes* will take effect next week, on Tuesday, May 14. Please make sure any custom tooling using these paths has been updated. If you have any questions or concerns, please reply-all to this email. Thanks! * in case you forgot, changes include: 1

[Puppet-dev] Re: Puppet repository moving from mocha to rspec-mocks

The 5.5.x, 6.0.x, 6.4.x, and master branches all have been switched over to use rspec-mocks as of yesterday. We'll be going through any outstanding PRs to the Puppet repository to see what will need to be updated to no longer use mocha. If you have any questions, please don't hesitate to ask. On W

[Puppet-dev] Re: Announcement: Release of Facter 3.11.0 gem

hello, Are there any plans to iterate on this to the point of getting a facter binary shipped with it? On Tuesday, March 20, 2018 at 8:12:48 PM UTC+1, sean.m...@puppet.com wrote: > > Hey Folks! > > We are officially shipping a gem for Facter 3.11.0! There is both a source > and a set of precomp

[Puppet-dev] Re: Release of R10K 3

Resending this to all of the original lists of this email, since I don't personally have the answer. Thoughts, Puppeteers? On Wed, Sep 26, 2018 at 4:23 PM Jesse Reynolds wrote: > Very good, thanks Maggie. > > Random question but do you know if it's possible now to have r10k talk to > forge.puppe

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 6.0.1

FYI, the release of Puppet Platform 6.0.1 has been postponed to October 2 to increase the runway for potential "ship stopper" issues that may need to be fixed. On Tue, Sep 18, 2018 at 6:01 PM Kenn Hussey wrote: > Now that Puppet Platform 6.0.0 has been released (see here for details), I > would

[Puppet-dev] Re: [voxpupuli] Beaker 3 to Beaker 4 migration for puppet modules.

Hi, The final phase of our migration to Beaker 4 for modules is complete. puppet-module-gems has been released and the Puppet supported modules have been updated. We are aware of the difficulties around these changes and thank you for your contin

[Puppet-dev] Re: [voxpupuli] Puppet Apache Module

Hi Davin, according to RedHat RHEL 6 has End of maintenance support 2 (Product retirement) until November 30, 2020 and End of extended lifecycle support at June 30, 20124. (https://access.redhat.com/support/policy/updates/errata#Life_Cycle_Dates) Will you support the latest apache module with R

[Puppet-dev] Re: [Puppet Users] New CA CLI tools in Puppet Platform 5.5.5

Thanks for feedback, Gabriel! On Fri, Aug 24, 2018 at 5:49 AM Gabriel Filion wrote: > Hi there, > > On 2018-08-23 2:35 p.m., Maggie Dreyer wrote: > > In the 5.5.5 release of the Puppet Platform, we released a new > experimental > > command line tool for interacting with the Puppet CA. > > > > pu

[Puppet-dev] Re: Beaker 3 to Beaker 4 migration for puppet modules.

Hi, Yesterday 0.3.9 of puppet-module-gems was released. This adds Beaker 3 as a dependency for system tests. The added dependencies have upper bounds to prevent future major releases of those gems from affecting modules. The Puppet supported modul

[Puppet-dev] Re: [Announce] Release of PDK v1.6.1

Hi folks! I'm pleased to say that we *do* now have instructions for installing PDK with Homebrew or Chocolatey. See the Installing PDK page at https://puppet.com/docs/pdk/1.x/pdk_install.html for details. Best, Jean Bond Sr. Technical Writer On Thu, Jul 26, 2018 at 11:34 AM Bryan Jen wrote: >

[Puppet-dev] Re: [Announce] Release of PDK v1.6.1

Hey Everyone! I made a mistake in yesterday's announcement email! The docs for installing PDK via brew and chocolatey are not published yet. But for those that want to do it, you can install PDK via brew using the instructions here: https://github.com/puppetlabs/homebrew-puppet . And for Choco, it

[Puppet-dev] Re: Puppet agent 1.10.13 and Puppet Platform 5.3.7 and 5.5.2 are now available

Apologies for the followup. A better URL to the list of CVEs is https://puppet.com/docs/security-vulnerability-announcements. For convenience, here are direct links to the four disclosures for these releases: https://puppet.com/security/cve/CVE-2018-6516 https://puppet.com/security/cve/CVE-2018-6

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 5.5.2

Apologies for the delayed update, but we'll be shipping this release today, June 7. On Wed, May 30, 2018 at 8:37 PM, Kenn Hussey wrote: > Unfortunately we have uncovered additional issues which require us to > postpone this release again. I will follow up with a new target date as > soon as one

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 5.5.2

Unfortunately we have uncovered additional issues which require us to postpone this release again. I will follow up with a new target date as soon as one is available. On Thu, May 24, 2018 at 3:41 PM, Kenn Hussey wrote: > We encountered issues while testing that will require us to ship this > re

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 5.5.2

We encountered issues while testing that will require us to ship this release later than originally planned. Our new target date is May 31, also reflected below. On Wed, May 9, 2018 at 4:45 PM, Kenn Hussey wrote: > We have decided to ship this release earlier than originally planned in > order t

[Puppet-dev] Re: Scope and Timeline for Puppet Platform 5.5.2

We have decided to ship this release earlier than originally planned in order to get some critical fixes into an official release sooner. See below for updated target milestone dates. On Fri, Apr 20, 2018 at 9:41 AM, Kenn Hussey wrote: > Now that Puppet Platform 5.5.1 has shipped, I would like t

Re: [Puppet-dev] Re: Announcement: Release of Bolt 0.19.1

Check out the hands-on lab: https://github.com/puppetlabs/tasks-hands-on-lab On Tue, May 1, 2018 at 1:14 PM Joaquin Menchaca wrote: > Any good tutorials on tasks/plans, creating tasks/plans, injecting data > into puppetdb or custom facts? Docs very sparse. For command and script, > had to wal

[Puppet-dev] Re: Announcement: Release of Bolt 0.19.1

Any good tutorials on tasks/plans, creating tasks/plans, injecting data into puppetdb or custom facts? Docs very sparse. For command and script, had to walk through source code at docs to get my experiments to work. On Monday, April 30, 2018 at 11:16:26 AM UTC-7, Kate Lopresti wrote: > > Hell

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

Interesting. Maybe I missed this detail. So, if I had 5 different 'vendored' locations across my filesystem, and they were all in my environment configuration, the Puppetfile would dictate which items from these locations would actually be used? I think I can get behind that. My concerns were bo

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan wrote: > Oh, and you're possibly setting yourself up for SERVER-94 hell if you're > not EXTREMELY careful. > Yep, I'm aware of the issues with environment isolation, as I filed the initial redmine ticket more than 5 years ago describing the problem

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

On Thu, Apr 26, 2018 at 7:42 PM, Trevor Vaughan wrote: > I would ask that you only vendor items that are super generic and that you > namespace them such that they won't interfere with people already written > codebases. > For modules that were previously in core puppet, we are plan on appending

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

Oh, and you're possibly setting yourself up for SERVER-94 hell if you're not EXTREMELY careful. On Thu, Apr 26, 2018 at 10:42 PM, Trevor Vaughan wrote: > I would ask that you only vendor items that are super generic and that you > namespace them such that they won't interfere with people already

Re: [Puppet-dev] Re: Moving non-core types and providers out of puppet

I would ask that you only vendor items that are super generic and that you namespace them such that they won't interfere with people already written codebases. The following seem relatively safe since they've been in use for quite some time: - stdlib - archive (maybe) - inifile - pow

[Puppet-dev] Re: Moving non-core types and providers out of puppet

Some people raised concerns about vendoring modules in the puppet-agent package[1]. I wanted to provide some more context about the "why", and some refinements to the "how". First, new users should be able to download the puppet-agent package and manage basic resources for the platform they're run

[Puppet-dev] Re: Custom Hiera Interpolation Functions

On 18/04/18 03:56, adam.gard...@magicmemories.com wrote: So, I'm aiming to have a method of interpolating Facter facts in Hiera data files that works more or less exactly like the `scope` lookup function, except that if the Facter fact is not defined, this interpolation should result in Hiera m

Re: [Puppet-dev] Re: Ephemeral resources

In terms of the 'after all resources processed' I think this is one of those cases where you present the capability because there is need and caveat it with the fact that you may, or may not, have access to resources that have been modified after the fact. In theory, with a hook like this, you cou

[Puppet-dev] Re: Ephemeral resources

On 16/04/18 23:13, Trevor Vaughan wrote: I thought there were dangers with Virtual Resource being accidentally realized sometimes? Not without users doing something bad (like realizing all) - puppet itself does not realize virtual resources willy-nilly. We found a super-hacky way to call f

Re: [Puppet-dev] Re: Ephemeral resources

I thought there were dangers with Virtual Resource being accidentally realized sometimes? We found a super-hacky way to call functions at the end of a compile which we use in https://github.com/simp/pupmod-simp-compliance_markup/blob/master/manifests/map.pp. It would be *really nice* if there were

[Puppet-dev] Re: Ephemeral resources

On 16/04/18 17:38, Trevor Vaughan wrote: How difficult would it be to create a third type of resource which is an 'ephemeral resource' whose only purpose is data collection on a host to be used by some other collector? These items would not be part of the catalog or added to the graph but wou

Re: [Puppet-dev] Re: Ephemeral resources

In terms of #2, there's actually a ticket that I put in a while ago for a shared data cache. But, I recently realized that the common pattern is to literally map every line in a file as a separate resource. We've had the same issue with firewall rules, etc... for quite some time. So, the most "use

[Puppet-dev] Re: Ephemeral resources

On Monday, April 16, 2018 at 10:38:55 AM UTC-5, Trevor Vaughan wrote: > > How difficult would it be to create a third type of resource which is an > 'ephemeral resource' whose only purpose is data collection on a host to be > used by some other collector? > > These items would not be part of th

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

Thanks for your tips Reid, especially the bit about "data_hash". I'll be sure to keep that in mind if I end up writing such a backend. Unfortunately there's no budget for this, so would definitely be an 'in-house' job. It's possible that I might be able to use the http_data_hash plugin you ment

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

Thanks for that John, If I go down this road, I'll post any code that I produce on GitHub and see if anyone else is interested in trying/testing it. Cheers, Nick On Tuesday, April 3, 2018 at 12:47:37 AM UTC+10, John Bollinger wrote: > > > > On Saturday, March 31, 2018 at 5:59:12 AM UTC-5, n

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

Hey Nick, A particular phrase you used caught my attention: "Elasticsearch holds the Hiera config for a number of nodes." There's a lot about putting together the words "elasticsearch" and "hiera backend" that can sound scary if it's done wrong, but I have seen backends built to solve the "con

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

On Saturday, March 31, 2018 at 5:59:12 AM UTC-5, nick@countersight.co wrote: > > Thanks for your response John, > > I appreciate you taking a quick look around to see if anyone else has > already done this. I had come to the same conclusion, that if someone has > already, they mostly like

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

Thanks for your response John, I appreciate you taking a quick look around to see if anyone else has already done this. I had come to the same conclusion, that if someone has already, they mostly likely haven't shared it. You raise valid points about EL being generally pretty unsuitable as a

[Puppet-dev] Re: Has anyone already developed an Elasticsearch backend to Hiera?

On Wednesday, March 28, 2018 at 12:19:58 AM UTC-5, nick@countersight.co wrote: > > Hi, > > I'd like to be able to store (and more importantly) retrieve Hiera hash > data from Elasticsearch for my Puppet runs. Does anyone know if this has > already been done? > I haven't heard of such a

[Puppet-dev] Re: Breaking Changes for Facter 4

On Wed, Mar 21, 2018 at 5:07 PM Branan Riley wrote: > Hey all, > > I spent a block of time this afternoon doing a pass at the Facter backlog, > and I believe I've flagged all the tickets that should land in a breaking > release. This doesn't mean we've committed to doing them, just that I'm not >

[Puppet-dev] Re: cfacter 3.11.0 pre-release gems available on rubygems

An update to this: After some testing we found out that the renaming the gem (to avoid conflicting with facter 2 gems) was not a good user experience. So we have instead release facter 3.11.0 as a 'pre-release' gem under the facter namespace. More info here: https://groups.google.com/forum/#!t

[Puppet-dev] Re: puppet5-nightly repos coming soon to nightlies.puppet.com!

Hey Puppet Users! puppet5 nightlies are finally live at nightlies.puppet.com! We've done our best to make this transition smooth, but if you run into issues or have any questions, please let us know! Thanks! On Tue, Jan 2, 2018 at 11:26 AM, Molly Waggett wrote: > Hello Puppet Users! > > We a

[Puppet-dev] Re: Feature Flags location

On 16/02/18 04:56, Juan Hoyos wrote: Hi there! In the COMMITTERS.md [0] file it is clearly stated that Puppet uses Feature Flags as the primary opt-in behavior, but cannot find a clear location where these are being used. In defaults.rb [1] I see configuration settings without no explicit dis

Re: [Puppet-dev] Re: Announce: Puppet Platform 5.3.4 is now available

The "no implicit conversion of nil into String" error should be fixed with the recent release of "gettext-setup"[1][2]. While this resolves the issue seen in modules CI with puppet-agent 5.3.4, there was an unrelated regression in the same release, involving non-default environments[3]. So I'd reco

[Puppet-dev] Re: Announce: Puppet Platform 5.3.4 is now available

Just for community awareness, there appears to be a breaking interaction between this latest Puppet release and rspec-puppet. Tests are failing with 'no implicit conversion of nil into String'. Already raised on PL tracker as PUP-8418 [1], and I've just raised against rspec-puppet [2]. So fo

[Puppet-dev] Re: Accidental Tags deleted from puppetlabs/facter

Actually, it applied to the following repos: facter, puppet, leatherman, pxp-agent, hiera, mcollective. The tags have now been removed. On Mon, Oct 30, 2017 at 4:16 PM Michael Smith wrote: > While testing some release automation, tags were accidentally pushed to > the https://github.com/puppetla

[Puppet-dev] Re: From foreman to my Iot Platform

I'm not sure if this is the answer to your question, but, because I don't know a lot about foreman. I do know quite a lot about Puppet and if this a Puppet related question, I guess you need to write a device type for the devices you want to manage. Here

[Puppet-dev] Re: Puppetserver, never-ending requests and watchdogs

On 21/08/17 09:22, Nacho Barrientos wrote: Hi, I'd like to bring up a point that was raised during the resolution of a ticket. The idea is to hopefully trigger a discussion and derive actions from it, if necessary. Bugs like the one described in PUP-7848 [0] (for which there's a fix already

Re: [Puppet-dev] Re: Announce: puppet server 2.8.0 available!

Hi Matthew, Thank you for pointing this out. The puppetserver 2.8.0 is available at https://downloads.puppetlabs.com/puppet/ On Sat, Sep 2, 2017 at 6:21 PM 'Matthew Thode' via Puppet Developers < puppet-dev@googlegroups.com> wrote: > It looks like the tarball is missing from > https://downloads.

[Puppet-dev] Re: Announce: puppet server 2.8.0 available!

It looks like the tarball is missing from https://downloads.puppetlabs.com/puppet/ . Please upload it as I use it for packaging (the base of what we install on Gentoo). Thanks, -- Matthew Thode -- You received this message because you are subscribed to the Google Groups "Puppet Developers" g

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

As an update to this odd issue, I did a puppet module generate to create a fresh directory setup and then copied in the the Puppet code, templates and spec files from the old one. Oddly it had no problems without any code modification that I can find anywhere. The same applies to using the PDK t

Re: [Puppet-dev] Re: lookup from external script

> There are however several use cases where people want to be able to > instantiate "a hiera" with a hierarchy of their own to do lookups. There > is the beginnings of such an API in puppet, but it is not well > documented and needs a bit more work. And example, like the one I sent, would totally

[Puppet-dev] Re: lookup from external script

On 21/08/17 09:26, Peter Meier wrote: Hi all, I have a bunch of ruby script that are munging data around, part of that data is based out of hiera. Until now, with hiera 3, I just required hiera in my ruby script, called lookup with a certain scope and I got my data out of hiera. Now looking fo

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

*Continued:* # /usr/local/share/gems/gems/puppet-4.10.4/lib/puppet/pops/functions/function.rb:45:in `call' # :2:in `block in call_function' # /usr/local/share/gems/gems/puppet-4.10.4/lib/puppet/pops/evaluator/runtime3_support.rb:313:in `eval' # /usr/local/share/gems/gems

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

# Continued # /usr/local/share/gems/gems/puppet-4.10.4/lib/puppet/pops/functions/function.rb:45:in `call' # :2:in `block in call_function' # /usr/local/share/gems/gems/puppet-4.10.4/lib/puppet/pops/evaluator/runtime3_support.rb:313:in `eval' # /usr/local/share/gems

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

So let me try this again. Here is the full init.pp and spec file being used. The setup is very simple. Likewise it does't matter if the *$sshd_hostkey_rhel_cent_7 *is setup as a smart parameter or set inside the module itself, the error "*Evaluation Error: Error while evaluating a Function C

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

So let me try this again. Here is the full init.pp and spec file being used. The setup is very simple. Likewise it does't matter if the *$sshd_hostkey_rhel_cent_7 *is setup as a smart parameter or set inside the module itself, the error "*Evaluation Error: Error while evaluating a Function C

[Puppet-dev] Re: Rspec giving no implicit conversion of Hash into String for an array

On Wednesday, August 16, 2017 at 11:51:30 AM UTC-5, James Perry wrote: > > I am getting an odd error when running rake spec on my module. The > functions work fine when setup in Puppet, but when I try to test it rspec > is kicking out an error about my $myarr arrays. When I comment it out, th

[Puppet-dev] Re: dependency error while running windowsfeature

I'm facing the same issue while trying run iis module in windows server 2012 R2. Could you please elaborate on how did you solve the issue? Thanks, Rakshatha On Friday, October 16, 2015 at 7:12:26 PM UTC+5:30, Salim Padela wrote: > > Environment: > > > Agent node: Windows Server 2012 R2 > > > Th

Re: [Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

On Fri, Aug 11, 2017 at 12:19 PM, Corey Osman wrote: > Do you guys have plans to bundle the puppet debugger in the pdk? I can't > think of a more useful tool then a repl and debugger to be part of > development kit. > No current plan to do so and we're in listening mode about where the most ben

[Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

Do you guys have plans to bundle the puppet debugger in the pdk? I can't think of a more useful tool then a repl and debugger to be part of development kit. Also will the pdk releases coincide with PE releases? I would want to make sure I am developing on the same platform that my code is r

Re: [Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

On 11 August 2017 at 19:06, Corey Osman wrote: > I haven't messed with PDK yet. What problems is this new tool solving > though? How is it different from puppet-retrospec? > https://github.com/nwops/puppet-retrospec > The main problems the PDK attacks today are - *Complexity of setting up

[Puppet-dev] Re: [ANN] Puppet Development Kit (pdk) preview (0.6.0)

I haven't messed with PDK yet. What problems is this new tool solving though? How is it different from puppet-retrospec? https://github.com/nwops/puppet-retrospec Bundling ruby was a good idea and all the gems. Corey On Tuesday, August 8, 2017 at 7:58:39 PM UTC-7, Lindsey Smith wrote: > >

[Puppet-dev] Re: Hiera Merge

On 10/08/17 20:48, ggun wrote: Thanks, but the main point to merge the hash is that the sub hash header value is not fixed in the example I have mentioned as esa-user-profile-service or esa-group-service. It can be anything. I need to make the code free from using direct Key value . So 'wa

[Puppet-dev] Re: Hiera Merge

Thanks, but the main point to merge the hash is that the sub hash header value is not fixed in the example I have mentioned as esa-user-profile-service or esa-group-service. It can be anything. I need to make the code free from using direct Key value . On Wednesday, August 9, 2017 at 2:24:34

[Puppet-dev] Re: Hiera Merge

If you're just trying to transform the data in Puppet code and assuming (as Henrik was) that you can't change how the data is stored, something like this might work. # Assuming $was_data is the hash of data from Hiera $common_data = $was_data.filter |$pair| { $pair[0] != 'was_dmgr_data' } $hash1

[Puppet-dev] Re: Hiera Merge

Thanks On Tuesday, August 8, 2017 at 7:10:13 PM UTC-4, ggun wrote: > > Hi Experts, > > I have a requirement as below. > I need to create a Hash from below hiera data. > > was_data: > hs3sourcepath: 'glic.binaries/websphere' > hdaresponse_file: /opt/software/WAS8.5.5.10_Install.xml > hibmagen

[Puppet-dev] Re: Hiera Merge

On 09/08/17 01:10, ggun wrote: Hi Experts, I have a requirement as below. I need to create a Hash from below hiera data. was_data: hs3sourcepath: 'glic.binaries/websphere' hdaresponse_file: /opt/software/WAS8.5.5.10_Install.xml hibmagentpath: /opt/software/agent.installer.linux.gtk.x8

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

In case it helps anyone else, there is likely no need to fiddle with the Heap etc. The root cause in my case was somehow during an upgrade the master was unpinned from the "Pe Certificate Authority" nodegroup. I've seen it on a few boxes that were upgraded using nc_migrate tool FWIW. On Frida

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

cheers Ryan, I have read the guide and made changes, we'll see how it goes. On Friday, July 28, 2017 at 11:27:29 AM UTC-7, Ryan Whitehurst wrote: > > On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski > wrote: > >> Cheers mate. This version of PE is actually running java 7. >> > > Ah, well in that cas

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Friday, July 28, 2017 at 11:27:29 AM UTC-7, Ryan Whitehurst wrote: > > On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski > wrote: > >> Cheers mate. This version of PE is actually running java 7. >> > > Ah, well in that case bumping up the MaxPermSize will have an effect, but > the problem is sti

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Fri, Jul 28, 2017 at 9:01 AM, Mike Jeski wrote: > Cheers mate. This version of PE is actually running java 7. > Ah, well in that case bumping up the MaxPermSize will have an effect, but the problem is still almost certainly caused by too low of a heap size, so you should still read the infor

[Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

Cheers mate. This version of PE is actually running java 7. On Thursday, July 27, 2017 at 1:19:59 PM UTC-7, Mike Jeski wrote: > > Hi group, > > running PE 3.8.7 (while cleaning up code for upgrade to puppet 4) seeing > HttpClientException constantly in the puppetserver.log. > > WARN [o.e.

Re: [Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

On Thu, Jul 27, 2017 at 1:37 PM, Mike Jeski wrote: > Cheers, > the -XX:MaxPermSize= was there as part of the pe-puppetserver package. I > merely raised the value to 512m from 256m. > > Are you saying it is syntactically incorrect? > It's not syntactically incorrect, it just has no effect on Ja

[Puppet-dev] Re: odd log entry warning: com.puppetlabs.http.client.HttpClientException: Request cancelled

Cheers, the -XX:MaxPermSize= was there as part of the pe-puppetserver package. I merely raised the value to 512m from 256m. Are you saying it is syntactically incorrect? On Thursday, July 27, 2017 at 1:19:59 PM UTC-7, Mike Jeski wrote: > > Hi group, > > running PE 3.8.7 (while cleaning up cod

[Puppet-dev] Re: So how exactly the immutable hashes are supposed to be used?

On 13/07/17 19:00, Mariusz Gronczewski wrote: Hi, I've been slowly converting old 3.x codebase (which has seen days of 0.24...) to 4.x and there is a lot of following pattern used for hashes:' $hash = { "some" => "defaults" } if $thing_one == "is_true" { $hash["

[Puppet-dev] Re: So how exactly the immutable hashes are supposed to be used?

On Friday, July 14, 2017 at 8:52:05 PM UTC+2, John Bollinger wrote: > > > > On Friday, July 14, 2017 at 9:52:37 AM UTC-5, Mariusz Gronczewski wrote: >> >> Hi, >> >> I've been slowly converting old 3.x codebase (which has seen days of >> 0.24...) to 4.x and there is a lot of following pattern use

[Puppet-dev] Re: So how exactly the immutable hashes are supposed to be used?

On Friday, July 14, 2017 at 9:52:37 AM UTC-5, Mariusz Gronczewski wrote: > > Hi, > > I've been slowly converting old 3.x codebase (which has seen days of > 0.24...) to 4.x and there is a lot of following pattern used for hashes:' > > $hash = { > "some" => "defaults" > } > >

[Puppet-dev] Re: Beaker rspec, puppet_install_helper and Puppet 5

Hello Thomas, I have the same problem here, tried to use puppet_install_helper, but it only creates PC1 repos. I'll try to update the puppet_install_repo and send a PR to that team in a couple days. For now, I'm using my own vagrant boxes with puppet5 already installed. CentOS - https://app.v

[Puppet-dev] Re: Announce: Puppet 5 Platform Available!

Am Mittwoch, 28. Juni 2017 04:13:24 UTC+2 schrieb Eric Sorenson: > > I have run out of superlatives to try to express how excited I am for this > release: the Puppet 5 Platform is available for download now. > > great news ! just finished upgrading to Puppet 4 with puppetserver which already dr

[Puppet-dev] Re: Announce: Puppet 5 Platform Available!

On 28/06/17 16:31, Trevor Vaughan wrote: I'm seeing a lot of Warning: Defining "data_provider": "hiera" in metadata.json is deprecated. How do we successfully support both Puppet 4.7 (LTS) and Puppet 5 (Today) without this garbage popping up at every run? I don't want to kill any *real* deprec

[Puppet-dev] Re: puppet-lint triage today at 2000-2100 UTC

Ah, timezones are hard! It will be at 2000-2100 UTC, which is 1600-1700 Eastern. Sorry for the confusion. On Thursday, June 15, 2017 at 8:03:56 AM UTC-4, Rob Nelson wrote: > > If you have issues/PRs or just interest in puppet-lint, the bi-monthly > triage is today at 1600-1700 UTC. > > BlueJean

[Puppet-dev] Re: Puppet Exception on windows 2016 server

Aditya - Another question I had is whether or not you have an event log message from the .NET crash that has any more detail? A stacktrace in particular would be helpful in tracking this down. On Thursday, May 25, 2017 at 6:19:40 AM UTC-7, Ethan Brown wrote: > > Hi Aditya - > > Do you have

  1   2   3   4   5   6   7   8   9   10   >