Jira (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode commented on PUP-9044 Re: Update puppet portage package provider for new output generated by qatom It looks like the code is in 4.x versions as well, do I need to backport it myself or wait for master to merge first? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9044) Update puppet portage package provider for new output generated by qatom
Title: Message Title Matthew Thode created an issue Puppet / PUP-9044 Update puppet portage package provider for new output generated by qatom Issue Type: Bug Assignee: Matthew Thode Components: Types and Providers Created: 2018/08/06 10:58 PM Priority: Normal Reporter: Matthew Thode Puppet Version: puppet-agent-5.5.4 Puppet Server Version: 5.3.4 OS Name/Version: Gentoo qatom output used to look like: qatom app-admin/puppet app-admin puppet (null) ...but now looks like... qatom app-admin/puppet app-admin puppet in app-portage/portage-utils-0.72 and above. Desired Behavior: the qatom output to be parsed correctly Actual Behavior: Error: Could not update: Execution of '/usr/bin/emerge -update app-admin/puppet' returned 1: !!! 'app-admin/puppet-' is not a valid package atom. Add Comment
Jira (PUP-8977) Add 'apply' statement to Plan language
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-8977 Add 'apply' statement to Plan language Change By: Michael Smith Assignee: Nick Lewis Michael Smith 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-745) Apply manifest block cannot use functions from boltlib from module that declares metadata
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-745 Apply manifest block cannot use functions from boltlib from module that declares metadata Change By: Michael Smith Assignee: Michael Smith 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title
Josh Cooper commented on PUP-9043
Re: file resource - mtime checksum does not seem to work
I can't reproduce this issue directly. Using puppet 4.10.9 and puppetserver-2.8.1-1.el7.noarch with manifest:
file { '/tmp/pl-build-tools-release-el-4.noarch.rpm':
ensure => file,
checksum => mtime,
source => 'https://artifactory.delivery.puppetlabs.net/artifactory/rpm__local/build-tools/yum/pl-build-tools-release-el-4.noarch.rpm',
}
Puppet downloads the file the first time. The second time it doesn't because the local file's mtime is greater than or equal to the desired time. Running with --http_debug shows the agent making the HEAD request, but doesn't make any changes because the file is insync:
<- "HEAD /artifactory/rpm__local/build-tools/yum/pl-build-tools-release-el-4.noarch.rpm HTTP/1.1\r\nAccept: */*\r\nUser-Agent: Ruby\r\nConnection: close\r\nHost: artifactory.delivery.puppetlabs.net\r\n\r\n"
-> "HTTP/1.1 200 OK\r\n"
-> "Server: Artifactory/X.X.X\r\n"
-> "X-Artifactory-Id: afec80514c436b4eadb7d267da0a18a8b6e8377d\r\n"
Jira (BOLT-745) Apply manifest block cannot use functions from boltlib from module that declares metadata
Title: Message Title
Michael Smith created an issue
Puppet Task Runner / BOLT-745
Apply manifest block cannot use functions from boltlib from module that declares metadata
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/08/06 4:06 PM
Priority:
Normal
Reporter:
Michael Smith
Given a module that declares metadata, a plan that applies a manifest block that tries to call a function from Bolt's internal module will fail to find the function.
metadata
{
"version": "0.1.0",
"author": "Anyone, really.",
"license": "Apache-2.0",
"source": "",
Jira (PUP-9010) Puppetserver fails to compile catalog when disable_i18n = true
Title: Message Title Vadym Chepkov commented on PUP-9010 Re: Puppetserver fails to compile catalog when disable_i18n = true PE2018.1.3 is affected as well 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-744) Doc errors in "run_script" examples
Title: Message Title
Eric Griswold created an issue
Puppet Task Runner / BOLT-744
Doc errors in "run_script" examples
Issue Type:
Bug
Affects Versions:
BOLT 0.21.5
Assignee:
Unassigned
Components:
DOCS
Created:
2018/08/06 2:50 PM
Priority:
Minor
Reporter:
Eric Griswold
2 small doc errors on the https://puppet.com/docs/bolt/0.x/plan_functions.html page under "run_script" Example: Run a module-provided script with arguments file_upload('iis/setup.ps1', $target, 'arguments' => ['/u', 'Administrator'])
Example: Run a script file_upload('/var/tmp/myscript', $targets, 'Downloading my application') In both cases, I think "file_upload" should be "run_script"
Add Comment
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Rob Braden updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Rob Braden Sprint: Platform Core Grooming 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Rob Braden updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Rob Braden Team: Platform Core OS 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9033) Confirm and describe type-specific behavior when omitting the ensure attribute
Title: Message Title Jorie Tappa commented on PUP-9033 Re: Confirm and describe type-specific behavior when omitting the ensure attribute Additional discussion is necessary about whether we should unify the behavior in addition to documenting the state of the world 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2983) Environment not updated via ENC if obsolete Environment in agents puppet.conf
Title: Message Title Eric Sorenson commented on PUP-2983 Re: Environment not updated via ENC if obsolete Environment in agents puppet.conf This was the oldest bug but most of the work is tracked under PUP-6802 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9038) Ability to pass variables into puppet lookup
Title: Message Title Jorie Tappa assigned an issue to Unassigned Puppet / PUP-9038 Ability to pass variables into puppet lookup Change By: Jorie Tappa Assignee: Thomas Hallgren 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9038) Ability to pass variables into puppet lookup
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9038 Ability to pass variables into puppet lookup Change By: Jorie Tappa Sub-team: Language 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9042) pagination set to `false` breaks module installs
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9042 pagination set to `false` breaks module installs Change By: Jorie Tappa Team: Server Puppet Developer Experience 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9042) pagination set to `false` breaks module installs
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9042 pagination set to `false` breaks module installs Change By: Jorie Tappa Team: Server 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9043 file resource - mtime checksum does not seem to work Change By: Jorie Tappa Team: Coremunity 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-743) Document bolt-server API endpoints
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-743 Document bolt-server API endpoints Issue Type: Task Assignee: Unassigned Created: 2018/08/06 1:57 PM Priority: Normal Reporter: Lucy Wyman https://docs.google.com/document/d/1NGC_pVgIFm1gOOWaqMxBhbkvoyjZh3bnkYSivBQZYKc/edit# Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-742) Add 'collection' parameter for install tasks
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-742 Add 'collection' parameter for install tasks Issue Type: Sub-task Assignee: Unassigned Created: 2018/08/06 1:54 PM Priority: Normal Reporter: Michael Smith Add a collection parameter accepting Enum[PC1, puppet5, puppet6] (default puppet5) to the install task (all platforms). It should allow installing from any of those collections. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8977) Add 'apply' statement to Plan language
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet / PUP-8977 Add 'apply' statement to Plan language Change By: Michael Smith Assignee: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-717) Ruby API to call bolt from
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-717 Ruby API to call bolt from Change By: Michael Smith Sprint: Bolt Ready for Grooming Discover/Design 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-678) Improve powershell task error handling
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-678 Improve powershell task error handling Change By: Michael Smith Sprint: Bolt Ready for Grooming Discover/Design 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
Change By:
Michael Smith
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.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9043) file resource - mtime checksum does not seem to work
Title: Message Title Jeff Sparrow created an issue Puppet / PUP-9043 file resource - mtime checksum does not seem to work Issue Type: Bug Assignee: Unassigned Created: 2018/08/06 12:25 PM Labels: file checksum artifactory http Priority: Normal Reporter: Jeff Sparrow Puppet Version: 4.10.9 Puppet Server Version: 2.8.0 OS Name/Version: Windows 201x Describe your issue in as much detail as possible… The mtime checksum for a file resource, does not seem to work with Artifactory. I don't know if this extends into oter http resources, but we are seeing this issue with Artifactory for sure. I am aware of PUP-6114 for md5 checksum fixes, but this is for mtime. I am not sure if there is already a ticket open for this or not, but I didnt see one, so here this is. We have 70 some servers that all have this issue. Here is a file we are obtaining from artifactory, as you can see it has a last-modified time of: Last-Modified: Sat, 04 Aug 2018 08:19:42 GMT Here is a list of the server times of that file. The size of the file is drastically different on every server as well. Its a 1.4GB file and some servers only have a file size of 100KB.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Josh Cooper commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ Thanks all. Is there a specification for the serialization format? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Jeff Sparrow commented on PUP-6114 Re: Add support for Artifactory checksum headers and enable SHA1 checksum type Would love to see this implemented. Multiple vendors of our use artifactory for shares, chocolatey, builds, etc. We recently ran into a big headache where we realized files were not md5 checking, using artifactory and its `X-CheckSum-xxx`. As a side note, it also seems that `mtime` is also way off on numerous files vs. the artifactory (remote) `mtime`. Without this update, I will have to move all `file` resources that use artifactory, to a file uri. Which means having to move these to more of a file share type system. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6114) Add support for Artifactory checksum headers and enable SHA1 checksum type
Title: Message Title Tim Meusel commented on PUP-6114 Re: Add support for Artifactory checksum headers and enable SHA1 checksum type Hey puppet people. I'm highly interested into this issue. Any chance you can rereview the PR and work on it? Thanks in advance! 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title
Garrett Guillotte updated an issue
Puppet Strings / PDOC-262
Puppet Strings output of Puppet types is inconsistent with puppet doc
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.3 *Puppet Server Version:* N/A *OS Name/Version:* N/AWhen generating resource type docs content from Puppet code with Puppet Strings, there are several formatting issues, some unique to certain types and others consistent across all types. These might not be relevant in Platform 6 when many of these types are moved to modules, but they currently require manual reconciliation when compiling reference docs for Platform 5.*All Strings output in types* * The {{puppet doc}} output lists providers, but the Strings docs do not. For example, this is included in the doc output for the zfs type, but omitted from the Strings output:{code}providerThe specific backend to use for this `zfs`resource. You will seldom need to specify this --- Puppet will usuallydiscover the appropriate provider for your platform.Available providers are:* [`zfs`](#zfs-provider-zfs){code} * The {{puppet doc}} output lists supported or required features, but the Strings output does not. For example, this appears in the {{puppet doc}} output for the service type's enable attribute, but not in the Strings output: {code}Requires features enableable.{code}This occurs despite the required feature being listed in the type:{code}newproperty(:enable, :required_features => :enableable) do{code}and features have their own description strings, which aren't output:{code}feature :enableable, "The provider can enable and disable the service",{code} * Defaults in the Strings output are formatted intuitively unintuitively , as:{code}* Default for: `["osfamily", "solaris"] == `{code} * The {{puppet doc}} output instead generates:{code}* Default for `osfamily` == `solaris`.{code} * Neither the doc nor Strings output recognizes when multiple allowed values function identically and should ideally be listed together, such as {{true}} and {{yes}} or {{false}} and {{no}} in types using {{Puppet::Parameter::Boolean}}. * The provider support table generated at the end of several types is inconsistent between the {{puppet doc}} and Strings output. Specifically, the number of rows per column is inconsistent, and some providers are listed as supported or unsupported differently in each. One especially notable discrepancy is in the mcx type, where the only listed provider (mcxcontent) is listed as supported in the {{puppet doc}} output and as unsupported in the Strings output.*Issues with specific types:** exec, file*Symptom: Many attributes are missing.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/*}}.*filebucket*Symptom: The port attribute has no description in the Puppet Strings output, despite having a description in
Jira (PUP-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Jayant Sane commented on PUP-7834 Re: Change all calls to YAML.load into YAML.safe_load You are right - I too was indicating MarshalLoad has been implicitly enabled and hence had mistakenly wondered about cipher_test-v3.rb. My bad on cipher_test-v3.rb - for some reason these had ended up in my local puppet repo which I forgot to do a git status on. 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. For more options, visit https://groups.google.com/d/optout.
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 CC Josh Cooper Kris Bosland Jacob Helwig 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title
Garrett Guillotte updated an issue
Puppet Strings / PDOC-262
Puppet Strings output of Puppet types is inconsistent with puppet doc
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.3 *Puppet Server Version:* N/A *OS Name/Version:* N/AWhen generating resource type docs content from Puppet code with Puppet Strings, there are several formatting issues, some unique to certain types and others consistent across all types. These might not be relevant in Platform 6 when many of these types are moved to modules, but they currently require manual reconciliation when compiling reference docs for Platform 5.*All Strings output in types* * The {{puppet doc}} output lists providers, but the Strings docs do not. For example, this is included in the doc output for the zfs type, but omitted from the Strings output:{code}providerThe specific backend to use for this `zfs`resource. You will seldom need to specify this --- Puppet will usuallydiscover the appropriate provider for your platform.Available providers are:* [`zfs`](#zfs-provider-zfs){code} * The {{puppet doc}} output lists supported or required features, but the Strings output does not. For example, this appears in the {{puppet doc}} output for the service type's enable attribute, but not in the Strings output:{code}Requires features enableable.{code}This occurs despite the required feature being listed in the type:{code}newproperty(:enable, :required_features => :enableable) do{code}and features have their own description strings, which aren't output:{code}feature :enableable, "The provider can enable and disable the service",{code}* Defaults in the Strings output are formatted intuitively, as:{code}* Default for: `["osfamily", "solaris"] == `{code}* The {{puppet doc}} output instead generates:{code}* Default for `osfamily` == `solaris`.{code}* Neither the doc nor Strings output recognizes when multiple allowed values function identically and should ideally be listed together, such as {{true}} and {{yes}} or {{false}} and {{no}} in types using {{Puppet::Parameter::Boolean}}. * The provider support table generated at the end of several types is inconsistent between the {{puppet doc}} and Strings output. Specifically, the number of rows per column is inconsistent, and some providers are listed as supported or unsupported differently in each. One especially notable discrepancy is in the mcx type, where the only listed provider (mcxcontent) is listed as supported in the {{puppet doc}} output and as unsupported in the Strings output.*Issues with specific types:**file*Symptom: Many attributes are missing.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/*}}.*filebucket*Symptom: The port attribute has no description in the Puppet Strings output, despite having a description in the type:{code}newparam(:port)
Jira (FACT-1871) puppet daemon continually redeploys a Jenkins module
Title: Message Title John Adams created an issue Facter / FACT-1871 puppet daemon continually redeploys a Jenkins module Issue Type: Bug Assignee: Unassigned Created: 2018/08/06 11:39 AM Priority: Critical Reporter: John Adams We are using the Jenkins module () and have found that it can redeploy the same plugin every refresh cycle. We have identified differences between puppet facts and factor -p (facts has the plug while factor does not) which we believe is related. When we run puppet agent --test is does not exhibit the re-install but the daemon always does. This makes is difficult to debug the cause. 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
Garrett Guillotte updated an issue
Puppet Strings / PDOC-262
Puppet Strings output of Puppet types is inconsistent with puppet doc
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.3 *Puppet Server Version:* N/A *OS Name/Version:* N/AWhen generating resource type docs content from Puppet codewith code with Puppet Strings, there are several formatting issues, some unique to certain types and others consistent across all types. These might not be relevant in Platform 6 when many of these types are moved to modules, but they currently require manual reconciliation when compiling reference docs for Platform 5.*All Strings output in types* * The {{puppet doc}} output lists providers, but the Strings docs do not. For example, this is included in the doc output for the zfs type, but omitted from the Strings output:{code}providerThe specific backend to use for this `zfs`resource. You will seldom need to specify this --- Puppet will usuallydiscover the appropriate provider for your platform.Available providers are:* [`zfs`](#zfs-provider-zfs){code} * The {{puppet doc}} output lists supported or required features, but the Strings output does not. For example, this appears in the {{puppet doc}} output for the service type's enable attribute, but not in the Strings output: {code}Requires features enableable.{code}This occurs despite the required feature being listed in the type:{code}newproperty(:enable, :required_features => :enableable) do{code}and features have their own description strings, which aren't output:{code}feature :enableable, "The provider can enable and disable the service",{code} * Defaults in the Strings output are formatted intuitively, as: {code}* Default for: `["osfamily", "solaris"] == `{code} * The {{puppet doc}} output instead generates: {code}* Default for `osfamily` == `solaris`.{code} * Neither the doc nor Strings output recognizes when multiple allowed values function identically and should ideally be listed together, such as {{true}} and {{yes}} or {{false}} and {{no}} in types using {{Puppet::Parameter::Boolean}}. * The provider support table generated at the end of several types is inconsistent between the {{puppet doc}} and Strings output. Specifically, the number of rows per column is inconsistent, and some providers are listed as supported or unsupported differently in each. One especially notable discrepancy is in the mcx type, where the only listed provider (mcxcontent) is listed as supported in the {{puppet doc}} output and as unsupported in the Strings output.*Issues with specific types:**file*Symptom: Many attributes are missing.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/*}}.*filebucket*Symptom: The port attribute has no description in the Puppet Strings output, despite having a description in the t
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title
Garrett Guillotte updated an issue
Puppet Strings / PDOC-262
Puppet Strings output of Puppet types is inconsistent with puppet doc
Change By:
Garrett Guillotte
*Puppet Version:* 5.5.3*Puppet Server Version:* N/A*OS Name/Version:* N/AWhen generating resource type docs content from Puppet codewith Puppet Strings, there are several formatting issues, some unique to certain types and others consistent across all types. These might not be relevant in Platform 6 when many of these types are moved to modules, but they currently require manual reconciliation when compiling reference docs for Platform 5.*All Strings output in types* * The {{puppet doc}} output lists providers, but the Strings docs do not. For example, this is included in the doc output for the zfs type, but omitted from the Strings output:{ { code} } providerThe specific backend to use for this `zfs`resource. You will seldom need to specify this --- Puppet will usuallydiscover the appropriate provider for your platform.Available providers are:* [`zfs`](#zfs-provider-zfs){ { code} } * The {{puppet doc}} output lists supported or required features, but the Strings output does not. For example, this appears in the {{puppet doc}} output for the service type's enable attribute, but not in the Strings output:{ { code} } Requires features enableable.{ { code} } This occurs despite the required feature being listed in the type: { { code} } newproperty(:enable, :required_features => :enableable) do{ { code} } and features have their own description strings, which aren't output: { { code} } feature :enableable, "The provider can enable and disable the service",{ { code} } * Defaults in the Strings output are formatted intuitively, as:{ { code} } * Default for: `["osfamily", "solaris"] == `{ { code} } * The {{puppet doc}} output instead generates:{ { code} } * Default for `osfamily` == `solaris`.{ { code} } * Neither the doc nor Strings output recognizes when multiple allowed values function identically and should ideally be listed together, such as {{true}} and {{yes}} or {{false}} and {{no}} in types using {{Puppet::Parameter::Boolean}}.* The provider support table generated at the end of several types is inconsistent between the {{puppet doc}} and Strings output. Specifically, the number of rows per column is inconsistent, and some providers are listed as supported or unsupported differently in each. One especially notable discrepancy is in the mcx type, where the only listed provider (mcxcontent) is listed as supported in the {{puppet doc}} output and as unsupported in the Strings output.*Issues with specific types:**file*Symptom: Many attributes are missing.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/*}}.*filebucket*Symptom: The port attribute has no description in the Puppet Strings
Jira (PDOC-262) Puppet Strings output of Puppet types is inconsistent with puppet doc
Title: Message Title Garrett Guillotte created an issue Puppet Strings / PDOC-262 Puppet Strings output of Puppet types is inconsistent with puppet doc Issue Type: Bug Assignee: Unassigned Components: DOCS Created: 2018/08/06 11:35 AM Priority: Normal Reporter: Garrett Guillotte Puppet Version: 5.5.3 Puppet Server Version: N/A OS Name/Version: N/A When generating resource type docs content from Puppet codewith Puppet Strings, there are several formatting issues, some unique to certain types and others consistent across all types. These might not be relevant in Platform 6 when many of these types are moved to modules, but they currently require manual reconciliation when compiling reference docs for Platform 5. All Strings output in types The puppet doc output lists providers, but the Strings docs do not. For example, this is included in the doc output for the zfs type, but omitted from the Strings output: code provider The specific backend to use for this `zfs` resource. You will seldom need to specify this — Puppet will usually discover the appropriate provider for your platform. Available providers are: [`zfs`](#zfs-provider-zfs) code The puppet doc output lists supported or required features, but the Strings output does not. For example, this appears in the puppet doc output for the service type's enable attribute, but not in the Strings output: code Requires features enableable. code This occurs despite the required feature being listed in the ty
Jira (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title Branan Riley commented on PUP-8987 Re: add resource_api gem to puppet gemspec It will depend on FFI eventually (once we sort that out). That /shouldn't/ be needed master-side, right? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3832) puppetdb module config.ini mgmt should be in sync with rpm
Title: Message Title Rob Braden updated an issue PuppetDB / PDB-3832 puppetdb module config.ini mgmt should be in sync with rpm Change By: Rob Braden Labels: rampage 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-707) Docs for how to use 'apply' in a plan
Title: Message Title Michael Smith commented on BOLT-707 Re: Docs for how to use 'apply' in a plan Draft: https://docs.google.com/document/d/1yru5CE6bMqtZrGmrGJupv_fE0j-h7p27uWK2hT0LrBI/edit?usp=sharing 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Josh Cooper commented on PUP-7834 Re: Change all calls to YAML.load into YAML.safe_load AFAICT Security/MarshalLoad is included in the current .rubocop.yml configuration (for puppet not sure about other repos). I didn't see cipher_test-v3.rb is that a PE acceptance thing? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8446) Remove "puppet man" face application
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-8446 Remove "puppet man" face application Change By: Jacob Helwig Assignee: Jacob Helwig 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8578) Extract sshkeys type/provider into a module
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8578 Extract sshkeys type/provider into a module Change By: Jacob Helwig Release Notes Summary: The sshkey and ssh_authorized_keys types have been moved into the sshkeys_core module on the Forge. This module is being repackaged into puppet-agent so that it is available by default. Release Notes: New Feature 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8614) Add ruby 2.5.0 to travis and appveyor test matrices for puppet
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-8614 Add ruby 2.5.0 to travis and appveyor test matrices for puppet Change By: Sean McDonald Assignee: Sean McDonald Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-707) Docs for how to use 'apply' in a plan
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-707 Docs for how to use 'apply' in a plan Change By: Michael Smith Assignee: Michael Smith 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7834) Change all calls to YAML.load into YAML.safe_load
Title: Message Title Jayant Sane commented on PUP-7834 Re: Change all calls to YAML.load into YAML.safe_load Wonder if we need to either disable Marshal.Load cop/rule or exclude cipher_test-v3.rb file (two instances that are not under any of the excluded folders) 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-736) Make it easier to discover the local:true option for modules in the Puppetfile
Title: Message Title Michael Smith commented on BOLT-736 Re: Make it easier to discover the local:true option for modules in the Puppetfile That's definitely what I've done in https://github.com/MikaelSmith/bolt-wordpress-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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-736) Make it easier to discover the local:true option for modules in the Puppetfile
Title: Message Title Alex Dreyer commented on BOLT-736 Re: Make it easier to discover the local:true option for modules in the Puppetfile I think the issue is that this option is useful with "r10k puppetfile install" but it's considered dangerous with a control repo/code manager. Once we support "relative" paths in bolt config we should use "site" as a directory for modules outside the control repo. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-736) Make it easier to discover the local:true option for modules in the Puppetfile
Title: Message Title Michael Smith commented on BOLT-736 Re: Make it easier to discover the local:true option for modules in the Puppetfile It's probably worth pulling some common r10k patterns into the Bolt docs. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-736) Make it easier to discover the local:true option for modules in the Puppetfile
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-736 Make it easier to discover the local:true option for modules in the Puppetfile Change By: Michael Smith Labels: docs 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8614) Add ruby 2.5.0 to travis and appveyor test matrices for puppet
Title: Message Title Sean McDonald updated an issue Puppet / PUP-8614 Add ruby 2.5.0 to travis and appveyor test matrices for puppet Change By: Sean McDonald Sprint: Platform OS 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9042) pagination set to `false` breaks module installs
Title: Message Title
Craig Genner updated an issue
Puppet / PUP-9042
pagination set to `false` breaks module installs
Change By:
Craig Genner
Looks like this was introduced in 5.5.3 when trying to decode the url that's used to download a module from a forge server.File: `lib/puppet/forge.rb`Line: 110 (`uri = decode_uri(response['pagination']['next'])`)Error: `Error: undefined method `gsub' for false:FalseClass`This looks to be because `response['pagination']['next']` is set to false when I run it:`\{"pagination"=>{"next"=>false, "total"=>1} ,... `Fix: test that `response['pagination']['next']` is not set to `false`(I'll try and send in a merge request if I get time)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@
Jira (PUP-9042) pagination set to `false` breaks module installs
Title: Message Title
Craig Genner created an issue
Puppet / PUP-9042
pagination set to `false` breaks module installs
Issue Type:
Bug
Affects Versions:
PUP 5.5.3
Assignee:
Unassigned
Components:
Puppet Server
Created:
2018/08/06 9:21 AM
Priority:
Normal
Reporter:
Craig Genner
Looks like this was introduced in 5.5.3 when trying to decode the url that's used to download a module from a forge server. File: `lib/puppet/forge.rb` Line: 110 (`uri = decode_uri(response['pagination']['next'])`) Error: `Error: undefined method `gsub' for false:FalseClass` This looks to be because `response['pagination']['next']` is set to false when I run it: `{"pagination"=> {"next"=>false, "total"=>1} ,...` Fix: test that `response['pagination']['next']` is not set to `false` (I'll try and send in a merge request if I get time)
Add Comment
Jira (BOLT-735) #{owner} resolves to nothing in a container on Docker for Mac
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-735
#{owner} resolves to nothing in a container on Docker for Mac
Change By:
Alex Dreyer
Fix Version/s:
BOLT Next
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.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8460) ssh_authorized_key key update will fail on CentOS 7.4
Title: Message Title Jacob Helwig commented on PUP-8460 Re: ssh_authorized_key key update will fail on CentOS 7.4 Not a strict duplicate of PUP-3234, but definitely closely related. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Rick Sherman commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ We should be okay. Those modules are still unreleased and we can update them if 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Davin Hanlon commented on PUP-8597 Re: Modify rich data serialization to use shorter tags instead of __pcore_type__ Josh Cooper - from Rick Sherman's earlier comment it looks like it will. However, the YANG modules are not released, so we can make changes before we release them to account for this. Does that seem OK Rick Sherman Thomas Honey? 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-736) Make it easier to discover the local:true option for modules in the Puppetfile
Title: Message Title
Kevin Reeuwijk updated an issue
Puppet Task Runner / BOLT-736
Make it easier to discover the local:true option for modules in the Puppetfile
Change By:
Kevin Reeuwijk
Priority:
Normal Minor
Summary:
Give 'bolt puppetfile install' an option Make it easier to not delete existing discover the local:true option for modules in the Puppetfile
I'd like to be able to bundle my Bolt Task Plan with my application repo in a straightforward way. I've done this here for my Pipelines for Applications demo: [https://github.com/puppetlabs-seteam/PFA_NodeJS_SampleApp/tree/kevin]The Boltdir contains a Puppetfile for supporting modules and a custom 'sampleapp' module which contains my Bolt Task Plan to install all the prereqs for the application.Now ideally, my script would have just these 2 commands:{code}bolt puppetfile installbolt plan run sampleapp::prereqs{code}However if I run *bolt puppetfile install*, it will delete the sampleapp module and only install the modules in the Puppetfile. Since It took another engineer to teach me that there is no way to use a Boltdir with supporting modules together with different modulepath "local: true" option that contains the can be used to ensure r10k doesn't purge a pre-existing module with my plan ( s by name ) , I would need to make things . This capability will become more complicated than desired: * publish used for Bolt with the sampleapp module somewhere in a separate repo and put in the Puppetfile * checkout the code new apply function , run *bolt puppetfile install*, manually add the sampleapp module back in and push the code back to git.Right now I did the second option to get hence it working. The first option is the neatest, but I feel a simpler option should be available: {code}bolt puppetfile install --no-purge{code}This option would install better discoverable for new users to prevent them running into the modules in the Puppetfile but not delete existing modules in the Boltdir same problem .
Jira (PUP-8716) Remove puppet module generate functionality
Title: Message Title David Schmitt updated an issue Puppet / PUP-8716 Remove puppet module generate functionality Change By: David Schmitt Release Notes Summary: The deprecated `puppet module generate` command has been removed. Use the [pdk](https://puppet.com/docs/pdk/1.x/pdk_install.html)'s `new module` command instead. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title David Schmitt commented on PUP-8987 Re: add resource_api gem to puppet gemspec resource_api's only dependency is hocon, which is not used on the server-side. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8763) Remove puppet module build functionality
Title: Message Title David Schmitt updated an issue Puppet / PUP-8763 Remove puppet module build functionality Change By: David Schmitt Release Notes Summary: To reduce the amount of developer tooling installed on all agents, this version of puppet removes the `puppet module build` command. To continue building module packages for the forge and other repositories, install the [pdk](https://puppet.com/docs/pdk/1.x/pdk_install.html), or the community provided [puppet-blacksmith](https://rubygems.org/gems/puppet-blacksmith) on your development systems. [Needs PDK-1100 resolved before the `puppet-blacksmith` part is true.] 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8763) Remove puppet module build functionality
Title: Message Title David Schmitt updated an issue Puppet / PUP-8763 Remove puppet module build functionality Not sure in which category to file this (it's not really a new feature) I've filed it as a deprecation, which is not 100% correct either, as it is a removal. Needs PDK-1100 resolved before the `puppet-blacksmith` part is true. Change By: David Schmitt Release Notes Summary: To reduce the amount of developer tooling installed on all agents, this version of puppet removes the `puppet module build` command. To continue building module packages for the forge and other repositories, install the [pdk](https://puppet.com/docs/pdk/1.x/pdk_install.html), or the community provided [puppet-blacksmith](https://rubygems.org/gems/puppet-blacksmith) on your development systems. Release Notes: Deprecation Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
