[Puppet Users] r10k update
Hello, ICYMI r10k was deemed "feature complete" and we moved the project to a maintenance mode status. This was a result of internal prioritization activities at Puppet by Perforce. Even with something being “feature complete,” you are able to use r10k as normal with both Puppet Open Source and Puppet Enterprise. One unintended result of changing the project to maintenance mode was that the issue tracker was closed. We've heard the feedback that's important to have, so we will reopen the project in order to make that tracker available to the community. This will re-open the ability for community members to submit bugs and PRs for issues -- however, we will only be able to respond to the most critical issues. Puppet by Perforce is continually evolving Puppet Enterprise and evaluating areas of the product that should provide better value to our customers. Code Manager and its use of r10k has been evaluated in the past and will continue to be evaluated in the future. The placement of r10k into maintenance mode does not affect the plans for Code Manager in the short term, but we will continue to evaluate all other options as we move forward. We look forward to continuing to make Puppet Enterprise a better experience for all of our customers and appreciate all of the community’s help. We didn't do a really good job of communicating what is happening with r10k and we are sorry about this. In the future, we will work to ensure this information is shared in a better manner whether that is via our Puppet user google group or on Slack. Appreciate your time and patience with us, and again, we apologize for the communication error on our part. -- Micah Wilson (Product) & *Charlie Sharpsteen *(Support) Puppet by Perforce -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAK%3DsEhXjZsoRtoepwMMsho_gxiV1fWPCi%2BC9v7%2B_-7HW8w_csQ%40mail.gmail.com.
[Puppet Users] not possible to access parameters from subclass
Hi all,
I'm using puppet for quite some time - about 10 years - but now I have a
problem that I can not fix.
I hope someone here can help me. I tried to google the problem, but the
solutions I found did not work.
The things that I tried are still in as a comment.
I have created a puppet modul that should be updated to include a config
class (normaly called a params class).
I simplified my setup and attached it at the end.
In the class servicea I tried to access the variable from the config
class, but I'm apparently not able to.
Can someone help me?
I case it is important I'm running Orcharhino 6.1. The Puppet-agent is
puppet-agent-6.28.0-1.el8.x86_64.
The output of puppet agent -t is:
Notice: In Config the servertype is: Frontend-Server
Notice: /Stage[main]/Testa/Testa::Config[config]/Notify[In Config the
servertype is: Frontend-Server]/message: defined 'message' as 'In Config
the servertype is: Frontend-Server'
Notice: In Config the cluster_name is: mycluster
Notice: /Stage[main]/Testa/Testa::Config[config]/Notify[In Config the
cluster_name is: mycluster]/message: defined 'message' as 'In Config the
cluster_name is: mycluster'
Notice: In servicea the servertype is : Frontend-Server
Notice: /Stage[main]/Testa::Servicea/Notify[In servicea the servertype
is : Frontend-Server]/message: defined 'message' as 'In servicea the
servertype is : Frontend-Server'
Notice: in servicea the servicea_servicea are 1:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 1: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 1: '
Notice: in servicea the servicea_servicea are 2:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 2: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 2: '
Notice: in servicea the servicea_servicea are 3:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 3: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 3: '
Notice: in servicea the servicea_servicea are 4:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 4: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 4: '
Notice: Applied catalog in 10.88 seconds
So you see that the variable is available from the config class, but
only the variable from init.pp is still accessible from the serivea
class. From the config class the variable is not avilable.
Thanks for any hints in advanced
Greetings from Frankfurt / Germany.
CU
Jens Kühnel
This are the classes
# File init.pp
class testa (
$config = '',
$servertype = '',
) {
create_resources(testa::config, $config)
}
# File config.pp
define testa::config (
$cluster_name = '',
) {
# include testa
$servertype = $testa::servertype
notify{"In Config the servertype is: ${servertype}": }
notify{"In Config the cluster_name is: ${cluster_name}": }
include testa::servicea
}
# File servicea.pp
class testa::servicea {
#include testa::config
#Class[testa::config] -> Class[testa::servicea]
$servicea_cluster_name = $testa::config::servicea_cluster_name
notify{"In servicea the servertype is : ${testa::servertype}": }
notify{"in servicea the servicea_servicea are 1:
${::testa::config::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 2:
${testa::config::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 3:
${testa::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 4: ${servicea_servicea}": }
}
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/be575993-9f09-b142-8fd0-d533c8e6725b%40kuehnel.org.
[Puppet Users] not possible to access parameters from subclass
Hi all,
I'm using puppet for quite some time - about 10 years - but now I have a
problem that I can not fix.
I hope someone here can help me. I tried to google the problem, but the
solutions I found did not work.
The things that I tried are still in as a comment.
I have created a puppet modul that should be updated to include a config
class (normaly called a params class).
I simplified my setup and attached it at the end.
In the class servicea I tried to access the variable from the config
class, but I'm apparently not able to.
Can someone help me?
I case it is important I'm running Orcharhino 6.1. The Puppet-agent is
puppet-agent-6.28.0-1.el8.x86_64.
The output of puppet agent -t is:
Notice: In Config the servertype is: Frontend-Server
Notice: /Stage[main]/Testa/Testa::Config[config]/Notify[In Config the
servertype is: Frontend-Server]/message: defined 'message' as 'In Config
the servertype is: Frontend-Server'
Notice: In Config the cluster_name is: mycluster
Notice: /Stage[main]/Testa/Testa::Config[config]/Notify[In Config the
cluster_name is: mycluster]/message: defined 'message' as 'In Config the
cluster_name is: mycluster'
Notice: In servicea the servertype is : Frontend-Server
Notice: /Stage[main]/Testa::Servicea/Notify[In servicea the servertype
is : Frontend-Server]/message: defined 'message' as 'In servicea the
servertype is : Frontend-Server'
Notice: in servicea the servicea_servicea are 1:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 1: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 1: '
Notice: in servicea the servicea_servicea are 2:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 2: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 2: '
Notice: in servicea the servicea_servicea are 3:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 3: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 3: '
Notice: in servicea the servicea_servicea are 4:
Notice: /Stage[main]/Testa::Servicea/Notify[in servicea the
servicea_servicea are 4: ]/message: defined 'message' as 'in servicea
the servicea_servicea are 4: '
Notice: Applied catalog in 10.88 seconds
So you see that the variable is available from the config class, but
only the variable from init.pp is still accessible from the serivea
class. From the config class the variable is not avilable.
Thanks for any hints in advanced
Greetings from Frankfurt / Germany.
CU
Jens Kühnel
This are the classes
# File init.pp
class testa (
$config = '',
$servertype = '',
) {
create_resources(testa::config, $config)
}
# File config.pp
define testa::config (
$cluster_name = '',
) {
# include testa
$servertype = $testa::servertype
notify{"In Config the servertype is: ${servertype}": }
notify{"In Config the cluster_name is: ${cluster_name}": }
include testa::servicea
}
# File servicea.pp
class testa::servicea {
#include testa::config
#Class[testa::config] -> Class[testa::servicea]
$servicea_cluster_name = $testa::config::servicea_cluster_name
notify{"In servicea the servertype is : ${testa::servertype}": }
notify{"in servicea the servicea_servicea are 1:
${::testa::config::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 2:
${testa::config::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 3:
${testa::servicea_servicea}": }
notify{"in servicea the servicea_servicea are 4: ${servicea_servicea}": }
}
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/e6777d5b-413e-01cb-efbb-29018fa2483e%40kuehnel.org.
[Puppet Users] Puppet Forge is down
Hello, forgeapi.puppetlabs.com is currently serving 502s. forge.puppet.com is serving 500s. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/51EFDA1A-10CC-489A-9C7F-49080DB02A4D%40discourse.org.
[Puppet Users] Error: Could not run: cannot load such file -- net/ssh/telnet
Hi, I've come across the in subject error when trying to run puppet against a cisco device. I've exhausted my knowledge to troubleshoot this issue. Any pointers or place to check would be appreciated. Thanks $ puppet device --verbose --target cisco_device.puppetlabs.net Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Error: Could not run: cannot load such file -- net/ssh/telnet $ Contents of device.conf [cisco_device.puppetlabs.net] type cisco_ios url file:///etc/puppetlabs/puppet/cisco_device.puppetlabs.net.yaml $ Contents of cisco_device.puppetlabs.net.yaml "address": "192.168.192.119" "port": 22 "username": "cisco" "password": "cisco" "enable_password": "" -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5d0f88f6-cbfa-4193-b692-ab18a8e8673en%40googlegroups.com.
[Puppet Users] Could not run: cannot load such file -- net/ssh/telnet
Hi, Can anyone help with this error? $ puppet device --verbose --target cisco_device.puppetlabs.net Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Error: Could not run: cannot load such file -- net/ssh/telnet Thanks Mike -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f87aec14-a9b8-4c0c-adba-25206c76f7cdn%40googlegroups.com.
