Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Karsten Heymann commented on PUP-9564 Re: Puppet upgrades debian packages with pending updates when setting them on hold Alexandru Popa, Josh Cooper It is a bit difficult to write a functioning test for this bug because you need to create a situation where a package is reliably available in two versions, and doing this against the official debian repos creates a moving target that depends on the current debian package situation. I can think of two ways to achieve this: Either use https://snapshot.debian.org/ and add two dated repos with known different versions of a package, or create a minimal dummy debian package in two versions and ship a tiny local repository with these two packages as a test asset. If I can be of any help with either of these ways, just give me a note. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.36577.1559798700241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9495) Implement `print` method for `server_list_settings`
Title: Message Title Josh Cooper commented on PUP-9495 Re: Implement `print` method for `server_list_settings` Passed master CI in 51f8521859 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295966.1550015035000.36564.1559796900444%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9495) Implement `print` method for `server_list_settings`
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9495 Implement `print` method for `server_list_settings` Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.5.0 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PUP-3905) Disable ruby 2.1.5 automatically retrying idempotent http methods
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3905 Disable ruby 2.1.5 automatically retrying idempotent http methods Change By: Josh Cooper Release Notes Summary: Disables ruby's automatic HTTP retry mechanism which could incorrectly cause the same report to be submitted multiple times, increasing the load on the puppetserver report processor. Release Notes: Bug Fix 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65130.1422037228000.36560.1559796360850%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3905) Disable ruby 2.1.5 automatically retrying idempotent http methods
Title: Message Title Josh Cooper commented on PUP-3905 Re: Disable ruby 2.1.5 automatically retrying idempotent http methods Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/d942eb18399bc4172981dd26984419dd9967523f 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65130.1422037228000.36545.1559796181647%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1366) Overhaul user experience handling plan errors
Title: Message Title
Reid Vandewiele created an issue
Puppet Task Runner / BOLT-1366
Overhaul user experience handling plan errors
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/06/05 4:58 PM
Priority:
Normal
Reporter:
Reid Vandewiele
It isn't possible today for a plan author to formally signal to callers that the plan failed (surfacing an error without requiring the caller to provide distinct (and not bound by convention) code paths for "ok" vs. "error". E.g.
$results = case ($plan_result = run_plan('mymodule::myplan',
'_catch_errors' => true,
)) {
Error: { $plan_result.details['result_set'] }
default: { $plan_result }
}
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Garrett Guillotte commented on PDOC-262 Re: Puppet Strings output of Puppet types is inconsistent with puppet doc Thanks Jean Bond, this is noted in the ticket description (and also affects exec): Apparent cause: Strings does not include attributes defined externally of the main type file. In other words, only the attributes defined in lib/puppet/type/file.rb are output by Strings, and Strings outputs none of the attributes defined in lib/puppet/type/file/*. The missing file attributes are also detailed in DOC-3545, and the missing exec attributes are detailed in DOCUMENT-847. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.268188.1533580542000.36430.1559778120528%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Rob Braden commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation Nacho Barrientos David Moreno García - I think we may want to get some additional context regarding your use case. The primary concern right now is that this adds headers to all requests made by Puppet, not just requests to Puppet servers. If we do adopt this patch we'll want to be careful to document the behavior, as there is some potential for information leakage if users don't understand the behavior. It seems like it would be possible to configure puppet to only add the custom header when connecting to a defined set of infrastructure, but the way the http client code is currently implemented, it would be messy and complex. We do have some improvements planned that will help, but that doesn't address your immediate needs. The option exists now to change the User Agent string, does that help with your use case? If not, can you provide any other specifics that may help us understand what you're trying to accomplish? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300606.1552923936000.36403.1559777820616%40Atlassian.JIRA. For more options, visit
Jira (PUP-3905) Disable ruby 2.1.5 automatically retrying idempotent http methods
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3905 Disable ruby 2.1.5 automatically retrying idempotent http methods Change By: Josh Cooper Fix Version/s: PUP 6.5.0 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65130.1422037228000.36174.1559771221806%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3905) Disable ruby 2.1.5 automatically retrying idempotent http methods
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3905 Disable ruby 2.1.5 automatically retrying idempotent http methods Change By: Josh Cooper Sprint: Platform Core KANBAN 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.65130.1422037228000.36182.1559771222167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1365) run_command should accept a list of acceptable exitcodes
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1365 run_command should accept a list of acceptable exitcodes Issue Type: New Feature Assignee: Unassigned Created: 2019/06/05 2:14 PM Priority: Normal Reporter: Alex Dreyer This comes up frequently with trying to run puppet agent -t but is useful in some other circumstances too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title
Jean Bond commented on PDOC-262
Re: Puppet Strings output of Puppet types is inconsistent with puppet doc
Adding another issue here so that it's not lost before this ticket gets broken down: Slack discussion: https://puppetcommunity.slack.com/archives/C0W298S9G/p1559694938039700 file resource parameters listed at the top of the file.md page:
file { 'resource title':
path=> # (namevar) The path to the file to manage. Must be fully...
ensure => # Whether the file should exist, and if so what...
backup => # Whether (and how) file content should be backed...
checksum=> # The checksum type to use when determining...
checksum_value => # The checksum of the source contents. Only md5...
content => # The desired contents of a file, as a string...
ctime => # A read-only state to check the file ctime. On...
force => # Perform the file operation even if it will...
group => # Which group should own the file. Argument can...
ignore => # A parameter which omits action on files matching
Jira (BOLT-1359) Collect usage data for non-boltlib built-in functions
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1359 Collect usage data for non-boltlib built-in functions Change By: Melissa Amos Labels: docs_reviewed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310938.155932623.35922.1559766540407%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1345) Add navigation to bolt website
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1345 Add navigation to bolt website Change By: Melissa Amos Labels: docs_reviewed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310324.1559062195000.35926.1559766540670%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1342) Help text should only list options for that command
Title: Message Title Thomas Beech assigned an issue to Thomas Beech Puppet Task Runner / BOLT-1342 Help text should only list options for that command Change By: Thomas Beech Assignee: Thomas Beech 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310059.1558709649000.35830.1559764861083%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1364) upload_file to have more fine control over what can be copied if the target exists
Title: Message Title Shaigy Nixon created an issue Puppet Task Runner / BOLT-1364 upload_file to have more fine control over what can be copied if the target exists Issue Type: Improvement Assignee: Unassigned Created: 2019/06/05 12:02 PM Priority: Normal Reporter: Shaigy Nixon Instead of failing right away if the target exists, it will be nice to have more fine control over what can be copied in upload_file. Ex: copy files that doesn't exist in target directory, or ability to overwrite the default option and copy files even if it exists in the target directory etc. Right now mv fill fail underneath upload_file, if the target directory exists. mv: cannot move ‘/tmp/3a21e5bb-563c-499b-85cd-c1296e2ef6b6/enterprise’ to ‘/etc/puppetlabs/enterprise/enterprise’: Came across this error while trying to sync the enterprise_data on the master to other infra nodes in a plan.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Kris Bosland commented on PUP-2958 Re: Rapid-fire puppet runs cause race condition with SSL data Merged #7555 into master at b03cd0e. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.42950.1405977404000.35668.1559761025675%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1303) Provide a Bolt Docker Image
Title: Message Title Morgan Rhodes commented on BOLT-1303 Re: Provide a Bolt Docker Image I got a skeleton of a bolt container following the same pattern we use for puppet-agent at https://github.com/puppetlabs/bolt-vanagon/pull/106. There are a bunch of questions/to-do's /cc Cas Donoghue 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308633.1557866171000.35589.155976794%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9362) Identical test content with different descriptions
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9362 Identical test content with different descriptions Change By: Josh Cooper Release Notes: Not Needed 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.288698.1544725859000.35549.1559759400638%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4391) Transient: 'uniqueness-violation' error while creating PE Infrastructure node group during install
Title: Message Title
Shaigy Nixon created an issue
PuppetDB / PDB-4391
Transient: 'uniqueness-violation' error while creating PE Infrastructure node group during install
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
enterprise_pe-acceptance-tests_integration-system_pe_cert-regen_weekend_2019_0_x___292__2019-06-05__sut-files.tgz
Created:
2019/06/05 11:26 AM
Labels:
transient
Priority:
Normal
Reporter:
Shaigy Nixon
PE Infrastructure node group creation failed during install with 'uniqueness-violation' error in 2019.0.x cert_regen job
/Stage[main]/Puppet_enterprise::Console_services/Puppet_enterprise::Trapperkeeper::Pe_service[console-services]/Service[pe-console-services]: Triggered 'refresh' from 108 events
2019-06-05T06:11:05.094+00:00 - [Error]: Received an unexpected error response from the Node Manager service at https://s25nydmaa097qlc.delivery.puppetlabs.net:4433/classifier-api: 422 {"kind":"uniqueness-violation","msg":"Could not complete the request because it violates a group uniqueness constraint. A group already exists that has:\nname = PE Infrastructure\nenvironment_name = production","details":{"constraintName":"groups_name_environment_name","conflict":{"name":"PE
Jira (PUP-9718) Create a plan_information_service in Puppet and add it to the information_service
Title: Message Title Branan Riley updated an issue Puppet / PUP-9718 Create a plan_information_service in Puppet and add it to the information_service Change By: Branan Riley Sprint: Skeletor Kanban 20190605 , Skeletor Kanban 20190619 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309780.1558558495000.35484.155975838%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title Josh Cooper commented on PUP-2958 Re: Rapid-fire puppet runs cause race condition with SSL data Failed integration, it doesn't reclaim stale lockfiles [root@rllkgfa3qeth9t6 ~]# echo 23423 > /etc/puppetlabs/puppet/ssl/ssl.lock [root@rllkgfa3qeth9t6 ~]# puppet agent -t --certname test Error: Could not run: Another puppet instance is already running; exiting 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
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Matthias Baur commented on PDOC-254 Re: @hiera section for putting example hiera Henrik Lindberg Nope it isn't, it breaks syntax highlighting. We currently use the following as a workaround: # @summary My example summary # # Examples # # ```yaml # classes: # - my_example_class # ``` # # @param first_parameter Very important parameter I'm sure why it works, but i shows up in the generate documentation.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Henrik Lindberg commented on PDOC-254 Re: @hiera section for putting example hiera Sean Millichamp Isn't it possible to just do @example This is a bit of yaml ```yaml key: value ``` (code} 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.252028.1526935563000.35046.1559748600624%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (HI-613) Invalid relationship: Package[kibana] { require => Yumrepo['MISCELLANEOUS'] }, because Yumrepo['MISCELLANEOUS'] doesn't seem to be in the catalog
Title: Message Title
Kunal Mehta created an issue
Hiera / HI-613
Invalid relationship: Package[kibana] { require => Yumrepo['MISCELLANEOUS'] }, because Yumrepo['MISCELLANEOUS'] doesn't seem to be in the catalog
Issue Type:
Bug
Assignee:
Andre Keller
Created:
2019/06/05 8:26 AM
Priority:
Critical
Reporter:
Kunal Mehta
*Hiera Data definition for package profile::devops::kibana::install::package: 'kibana': ensure: latest require: Yumrepo['MISCELLANEOUS'] -- *Class definition for Package installation class profile::devops::kibana::install ( $config = undef, ) { # Set the global execution path. Exec \{ path => ['/sbin', '/bin', '/usr/sbin', '/usr/bin'] }
Install specified packages. $defaults = { ensure => 'installed', } if $config { #notify \{ "@1: $config <<<": } create_resources(package, $config, $defaults) } else { $hiera_config = hiera_hash('profile::devops::kibana::install::package', undef) #notify \{ "@2: $hiera_config <<<": } if $hiera_config { create_resources(package, $hiera_config, $defaults) } } }
if i am using ensure: latest it is installing default package from yum , if i am mentioning required repo for package to install package it is throwing the error mentioned in summary. Please suggest some workaround.
Jira (BOLT-1363) Singular version of TargetSpec data type
Title: Message Title Alex Dreyer commented on BOLT-1363 Re: Singular version of TargetSpec data type Henrik Lindberg Without fundamentally changing how we interact with targets it's not possible. If I pass in a string 'foo' to a TargetSpec get_targets} could resolve that string to a single target in inventory, a group with any number of targets or a target that is not part of the inventory. We could validate what it resolves to before the plan is called but that plan could update the inventory for example by adding targets to an empty group. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311260.1559685174000.34988.1559747401649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-924) Support kerberos puppetdb endpoint
Title: Message Title
Steve Traylen commented on BOLT-924
Re: Support kerberos puppetdb endpoint
Got a bit further with this , now with a configuration.
puppetdb:
krb: true
server_urls: ["https://constable.example.ch:9081"]
then
bolt command run uptime -q 'facts[certname] { name = "hostgroup" and value = "aiadm/nodes/login" }'
works as expected and queries puppetdb with a kerberos token. This is still using rubygem-curb, httpi and socksify as extra gem dependencies. There is probably a lighter way to do it. https://github.com/cernops/bolt/commit/addeb4fd2decddd3e59b3ee09bf1e74de4bfd291 and deps. https://github.com/cernops/puppet-runtime/commit/71ff7c0c94202436c8fab350bde8c2d01c3a8b7f https://github.com/cernops/puppet-runtime/commit/28fc46338b9f6bb5fca5a9359b3cc73d83028da3 I'll deploy this tommorow for for some user feedback.
Add Comment
Jira (PUP-9323) Resolve Deferred values on demand instead of at catalog read time
Title: Message Title Henrik Lindberg commented on PUP-9323 Re: Resolve Deferred values on demand instead of at catalog read time Hm, the actual difficulties with delaying Deferred resolution was not shown in this ticket. There are many resource types that visit all of their parameters early and thus force the resolution too early. The resource type may need the value early, and such a resource can thus never get late binding deferreds. This complicates everything in a way that isn't great for users, and could possibly be fixed for resources for parameters that are now just read without actually being required to be read early. The PR that is up is just delaying the deferred until the parameter is read. It is worth trying it out, but it won't work with some resources - notably File as it reads its parameters early. Very disappointing because it is the typical use case (File with template produced contents). 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.285576.154262828.34863.1559738940336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-859) System level configuration e.g /etc/puppetlabs/bolt
Title: Message Title Steve Traylen commented on BOLT-859 Re: System level configuration e.g /etc/puppetlabs/bolt Was advised to expand the use case here . So as well as central bolt configuration a central inventory file would also be useful. So typical case for is we have ~100 folk running remote procedures on puppet managed nodes. We would want to centrally maintain (with puppet) an inventory file and a configuration. We would centrally manage e.g puppetdb endpoints but in the inventory file we would also maintain maybe many groups of nodes represented as a puppetdb queries of the clusters which we already have our infrastructure split up into. In ideal world inventory files could be extended of over riden from a user based files but not a necessity. I think this ticket is an exact duplicate of BOLT-821 one by the way. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.277020.1537792033000.34857.1559738640575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Sean Millichamp commented on PDOC-254 Re: @hiera section for putting example hiera In my perfect world I'd like @lookup (and yes, you're right, a much better name than @hiera) to look and work more or less exactly like @param, near/in the param section. But maybe just auto-tagged with a "Not available as a class parameter" type message. I don't like the re-including all the @param docs again, it seems unnecessarily verbose bordering on confusing for a class with a very large set of parameters. Even with a @lookup tag, I still feel that there is a need for an additional @example-style tag for YAML-syntax highlighted groups of keys for specific use cases and complex behaviors requiring setting multiple keys to achieve specific results. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.252028.1526935563000.34851.1559738400478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9323) Resolve Deferred values on demand instead of at catalog read time
Title: Message Title Henrik Lindberg commented on PUP-9323 Re: Resolve Deferred values on demand instead of at catalog read time Michael Smith Good example. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.285576.154262828.34845.1559736960308%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-281) Add header autogeneration
Title: Message Title Henrik Lindberg commented on PDOC-281 Re: Add header autogeneration This sounds more like a task for puppet-lint where it is possible to add "auto corrections". 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311291.1559727925000.34841.1559736840173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Henrik Lindberg commented on PDOC-254 Re: @hiera section for putting example hiera I would prefer if there was a @lookup tag, and that it would work more or less as @param, i.e. you can state a data type and what it means. Then any yaml examples (or whatever is needed given whichever backend examples are provided for, that just uses the @example tag. The reason I want "lookup" as tag rather than "hiera" is that it is "lookup" everywhere else (function, CLI, "Automatic Parameter Lookup", etc.) - and that "hiera" is a particular implementation of lookup. What remains is to decide on what the output looks like - should for example all @param be included again in the lookup section and mixed with those that are explicitly looked up? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.252028.1526935563000.34836.1559736720225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9564) Puppet upgrades debian packages with pending updates when setting them on hold
Title: Message Title Alexandru Popa commented on PUP-9564 Re: Puppet upgrades debian packages with pending updates when setting them on hold Josh Cooper should I close this ticket since the PR for the fix was merged? 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300439.1552654564000.34831.1559736120363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Matthias Baur commented on PDOC-254 Re: @hiera section for putting example hiera For #2 most of my day-to-day user base is very familiar with making changes in Hiera/YAML, but they are not as familiar (in some cases, not at all) with Puppet class syntax and examples shown in Puppet class parameter declaration style wouldn't be nearly as meaningful/useful to them. Exactly the same for us! 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.252028.1526935563000.34804.1559733780239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-280) Rake Task for coverage
Title: Message Title Sean Millichamp commented on PDOC-280 Re: Rake Task for coverage I think this would be great, but I'd like to suggest that it to flag puppet-strings warnings of any kind, not just coverage. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311289.1559727679000.34801.1559733420204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Sean Millichamp commented on PDOC-254 Re: @hiera section for putting example hiera I like the idea of a @hiera tag. Though making the example syntax style configurable might be more flexible. I actually think that there may be two Hiera-related opportunities here: 1) Documenting keys which are used in lookup() calls which aren't class parameters similar to the style of "@param". Maybe the data type could even be sussed out of the lookup() call parameters, if listed. 2) Documenting example Hiera YAML blocks as they would look in the file. This would be more in keeping with the @example tag. To Henrik Lindberg's question, I'd like to think the value of #1 is self-evident. From a user standpoint "lookup()" only based keys are still parameters which are part of the interface. For #2 most of my day-to-day user base is very familiar with making changes in Hiera/YAML, but they are not as familiar (in some cases, not at all) with Puppet class syntax and examples shown in Puppet class parameter declaration style wouldn't be nearly as meaningful/useful to them. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit
Jira (PUP-9728) `puppet device --apply` no such file, state.yaml.lock
Title: Message Title David Mallon updated an issue Puppet / PUP-9728 `puppet device --apply` no such file, state.yaml.lock Change By: David Mallon Team: Network Automation 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311189.1559660438000.34777.1559730360557%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-254) @hiera section for putting example hiera
Title: Message Title Matthias Baur commented on PDOC-254 Re: @hiera section for putting example hiera What needs to be changed is this line --> https://github.com/puppetlabs/puppet-strings/blob/59428718a0ecbb639027aefc3cc40b7ade89e390/lib/puppet-strings/markdown/templates/classes_and_defines.erb#L41 I see to options: 1. Make it configurable in the @example 2. Add a @hiera tag as suggested by Eric Putnam 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.252028.1526935563000.34717.1559728080491%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-281) Add header autogeneration
Title: Message Title Matthias Baur created an issue Puppet Strings / PDOC-281 Add header autogeneration Issue Type: New Feature Assignee: Unassigned Created: 2019/06/05 2:45 AM Priority: Normal Reporter: Matthias Baur Given the following scenario (which I think is quite common): A user already has a working module, but the puppet strings documentation is missing/documented in other format. It would be great if puppet-strings could automatically generate the necessary header block (`# @params $parameter`, ...) for the user which then only had to fill out the missing things. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-280) Rake Task for coverage
Title: Message Title Matthias Baur created an issue Puppet Strings / PDOC-280 Rake Task for coverage Issue Type: New Feature Assignee: Unassigned Created: 2019/06/05 2:41 AM Priority: Normal Reporter: Matthias Baur It would be great if puppet-strings would support a Rake task which checks for documentation converge. This would allow a CI jobs which verifies that all parameters are documented. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1363) Singular version of TargetSpec data type
Title: Message Title Henrik Lindberg commented on BOLT-1363 Re: Singular version of TargetSpec data type Maybe it would be possible to use a constraint to TargetSpec on the number of targets the data type represents, like for Array and Hash data types? IIRC we did add support for type parameters for Object types which is required in order to be able to state something like TargetSpec[1] (exactly one target in the spec) - then if wanted, an alias type `SingleTarget` could be created for that. You still need to call get_targets, but no need to assert the count. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311260.1559685174000.34661.1559723760269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9706) Removing user on Solaris 11 with altered managehome
Title: Message Title Michael Smith updated an issue Puppet / PUP-9706 Removing user on Solaris 11 with altered managehome Change By: Michael Smith Fix Version/s: PUP 5.5.z 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308724.155793208.34639.1559719260786%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9706) Removing user on Solaris 11 with altered managehome
Title: Message Title Michael Smith updated an issue Puppet / PUP-9706 Removing user on Solaris 11 with altered managehome Change By: Michael Smith Fix Version/s: PUP 6.y Fix Version/s: PUP 6.0.z 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308724.155793208.34641.1559719260882%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
