Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title
Thomas Hallgren commented on PUP-7068
Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
The expected behavior is different depending on Hiera version. For version 3 (which this ticket is about) the "data_dir" is resolved against the current working directory (the directory returned by Dir.pwd()) of the puppet master process. If "data_dir" is left out, it defaults to:
File.join(Puppet.settings[:codedir], 'environments', '%{::environment}', 'hieradata')
Version 4 and 5 of Hiera considers the "data_dir" of the global configuration to be relative to parent of the Puppet setting "hiera_config" which in turn defaults to the setting of codedir + "/hiera.yaml", or if that is missing, the setting of confdir + "/hiera.yaml". The "data_dir" of an environment or module is always relative to the environment or module root.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from
Jira (BOLT-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-328) Don't pass task paths to run_task
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-328 Don't pass task paths to run_task Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-198 Add 'bolt task show' instructions to error message for incorrect task Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-313) Bolt didn't see tasks
Title: Message Title Nick Lewis commented on BOLT-313 Re: Bolt didn't see tasks It doesn't look like any of those modules actually contain tasks. Try installing the puppetlabs-package module and see if that appears in the task list. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-7398) deprecate puppet module generate
Title: Message Title Jean Bond updated an issue Puppet / PUP-7398 deprecate puppet module generate Change By: Jean Bond Labels: resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Josh Cooper commented on PUP-8463 Re: Remove existing warnings and run PRs through 'ruby -wc' Merged to master https://github.com/puppetlabs/puppet/commit/9c3a648758f5ad2918cc921b73ebd8c31802e68c, https://github.com/puppetlabs/puppet/commit/b5a63e27aa45958f861bbfe5e971bed7838018e6 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8464 puppet help should process its arguments better Change By: Eric Delaney Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8445) Deprecate "puppet man"
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Puppet / PUP-8445 Deprecate "puppet man" Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8445) Deprecate "puppet man"
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8445 Deprecate "puppet man" Change By: Eric Delaney Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3837) Update winston (PuppetDB 5.2.0)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3837 Update winston (PuppetDB 5.2.0) Change By: Jeff Yarnell Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3838) Queries to the facts endpoint generates jsonb_each
Title: Message Title Jeff Yarnell commented on PDB-3838 Re: Queries to the facts endpoint generates jsonb_each Jeff Yarnell Talk to CS about our delaying this for one sprint Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3838) Queries to the facts endpoint generates jsonb_each
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3838 Queries to the facts endpoint generates jsonb_each Change By: Jeff Yarnell Sprint: Data Platorm Platform 2018- 02 03 - 28 14 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3851) (docs) 5.2.x release notes
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3851 (docs) 5.2.x release notes Issue Type: Bug Assignee: Unassigned Created: 2018/02/14 2:42 PM Priority: Normal Reporter: gepetto-bot Release notes PR wound up on master. This cherry-picks them onto 5.2.x. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDB-3848) Release PuppetDB 5.1.z(2018-04-09)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3848 Release PuppetDB 5.1.z(2018-04-09) Change By: Nirupama Mantha Summary: Release PuppetDB 5. 2 1.z (2018-04-09) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3849) Release PuppetDB 5.1.z (2018-04-18)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3849 Release PuppetDB 5.1.z (2018-04-18) Change By: Nirupama Mantha Summary: Release PuppetDB 5.1. 4 z (2018-04-18) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney commented on PUP-8464 Re: puppet help should process its arguments better These commands all now print the puppet help with the list of subcommands: bx puppet help bx puppet help help bx puppet help help help $ bx puppet help help help Usage: puppet [options] [options] Available subcommands: agent The puppet agent daemon apply Apply Puppet manifests locally These command now prints the "help --help" --help output bx puppet help help help help
Jira (PDB-3850) Release PuppetDB 5.2(2018-04-17)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-3850 Release PuppetDB 5.2(2018-04-17) Issue Type: Task Assignee: Unassigned Created: 2018/02/14 2:23 PM Priority: Normal Reporter: Nirupama Mantha Release PDB for PE 2018.1.0 Irving https://confluence.puppetlabs.com/x/ToO3Bg Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDB-3849) Release PuppetDB 5.1.4 (2018-04-18)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-3849 Release PuppetDB 5.1.4 (2018-04-18) Issue Type: Task Assignee: Unassigned Created: 2018/02/14 2:19 PM Priority: Normal Reporter: Nirupama Mantha Release PDB for PE 2016.4.11 - Davis LTS Z https://confluence.puppetlabs.com/display/PM/PE+2016.4.11 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDB-3848) Release PuppetDB 5.2(2018-04-09)
Title: Message Title Nirupama Mantha updated an issue PuppetDB / PDB-3848 Release PuppetDB 5.2(2018-04-09) Change By: Nirupama Mantha Sprint: Data Platform 2018-03-28 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3848) Release PuppetDB 5.2(2018-04-09)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-3848 Release PuppetDB 5.2(2018-04-09) Issue Type: Task Assignee: Unassigned Created: 2018/02/14 2:08 PM Priority: Normal Reporter: Nirupama Mantha Release PDB in preparation for the Puppet Platform 5.3.6 release https://confluence.puppetlabs.com/x/tYfaCQ Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDB-3837) Update winston (PuppetDB 5.2.0)
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3837 Update winston (PuppetDB 5.2.0) Change By: Jeff Yarnell Sprint: Data Platform 2018-02-14 , Data Platorm 2018-02-28 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-338) Local transport for orchestrator
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-338 Local transport for orchestrator Change By: Alex Dreyer Executing tasks locally is a powerful method of extending the plan language without writing ruby. Currently bolt has to connect over a normal transport to execute local tasks. Instead bolt should have a special local transport that can be used.Users can target the local transport with the bare string "localhost"Users can target localhost with the protocol 'local'. The rest of the uri will be ignored.Implementation:Windows and linux code should be kept in separate classes with the executor deciding which version to load/use.The Inventory should be responsible for handling the host named 'localhost' and returning a host with the local transport.Questions:Should the transport copy task files before execution to make it more useful for iteration during task development? Eventually we may want both options what should we default to or implement first?Should linux and windows shell implementations be separate tickets? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-338) Local transport for orchestrator
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-338 Local transport for orchestrator Change By: Alex Dreyer Executing tasks locally is a powerful method of extending the plan language without writing ruby. Currently bolt has to connect over a normal transport to execute local tasks. Instead bolt should have a special local transport that can be used.Users can target the local transport with the bare string "localhost"Users can target localhost with the protocol 'local'. The rest of the uri will be ignored.Implementation:Windows and linux code should be kept in separate classes with the executor deciding which version to load/use.The Inventory should be responsible for handling the host named 'localhost' and returning a host with the local transport.Questions:Should the transport copy task files before execution to make it more useful for iteration during task development? Eventually we may want both options what should we default to or implement first? Should linux and windows implementations be separate tickets? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-338) Local transport for orchestrator
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-338 Local transport for orchestrator Issue Type: New Feature Assignee: Unassigned Created: 2018/02/14 1:24 PM Priority: Normal Reporter: Alex Dreyer Executing tasks locally is a powerful method of extending the plan language without writing ruby. Currently bolt has to connect over a normal transport to execute local tasks. Instead bolt should have a special local transport that can be used. Users can target the local transport with the bare string "localhost" Users can target localhost with the protocol 'local'. The rest of the uri will be ignored. Implementation: Windows and linux code should be kept in separate classes with the executor deciding which version to load/use. The Inventory should be responsible for handling the host named 'localhost' and returning a host with the local transport. Questions: Should the transport copy task files before execution to make it more useful for iteration during task development? Eventually we may want both options what should we default to or implement first? Add Comment
Jira (PUP-7068) Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml
Title: Message Title Eric Sorenson commented on PUP-7068 Re: Relative paths in a hiera v3 config must not be resolved against parent of hiera.yaml Thomas Hallgren this came up from a user on irc today - what is the expected behaviour when the running process is the puppet master? They wanted to use relative paths to the datadir to avoid hardcoding the whole filesystem path, making the puppet/hiera setup more relocatable. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8431) Communicate scope and timeline of next release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8431 Communicate scope and timeline of next release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13) 1. Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group.2. Create or update the Kanban board for the release. Ensure that the underlying filter for the board include issues from the release filter and add a quick filter to highlight just those issues.3. Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”.4. Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed.5. Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages.6. Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page.7. Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release. Add Comment This message was
Jira (PUP-8442) type parameters do not honor when default is set to false
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8442
type parameters do not honor when default is set to false
Change By:
Josh Cooper
Acceptance Criteria:
* parameter defaults of {{false}} are honored and properly set * false values are correctly stored in the last run report and corrective change transactionstore.yaml
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
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-3847) allTypes graphql resolver loads the whole database
Title: Message Title Russell Mull created an issue PuppetDB / PDB-3847 allTypes graphql resolver loads the whole database Issue Type: Bug Assignee: Unassigned Created: 2018/02/14 11:37 AM Priority: Normal Reporter: Russell Mull This is bad. Now that we have a real schemaStore, we should use that instead. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8465) support of backup attribute with the file_line resource
Title: Message Title Ravidatta Harishankar created an issue Puppet / PUP-8465 support of backup attribute with the file_line resource Issue Type: Improvement Assignee: Unassigned Created: 2018/02/14 11:36 AM Environment: As you may be aware that we have a file bucket resource which can be adopted to backup the files. however most of the files are getting edited via file_line and it is unfortunate that file_line resource does not supports the backup attribute like File resource. can we get that feature please? Thank you! Priority: Normal Reporter: Ravidatta Harishankar Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Jira (PUP-8444) Have "puppet man" default to "--help" when run without arguments
Title: Message Title Eric Delaney commented on PUP-8444 Re: Have "puppet man" default to "--help" when run without arguments Things to test: PAGER=cat bundle exec puppet man PAGER=cat bundle exec puppet man man PAGER=cat bundle exec puppet man man man PAGER=cat bundle exec puppet man cert PAGER=cat bundle exec puppet man ca PAGER=cat bundle exec puppet man crazy PAGER=cat bundle exec puppet man --help Add Comment
Jira (PUP-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Change By: Josh Cooper Fix Version/s: PUP Future Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-332) Target objects should store state of the Targets
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-332 Target objects should store state of the Targets Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Jacob Helwig Assignee: Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Jacob Helwig commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Konrad Scherer, I'm not able to reproduce this on the latest version of Puppet. If I have a duplicate resource in a manifest, I get a last_run_summary.yaml with the following content from an agent run: --- version: config: puppet: 5.4.0 time: last_run: 1518635813 If I run "puppet apply" with a manifest that has duplicate resources, the last_run_summary.yaml doesn't get updated at all. Is this still an issue for you? Add Comment
Jira (PUP-1329) composite namevars should be more robust
Title: Message Title Josh Cooper commented on PUP-1329 Re: composite namevars should be more robust Hi Edwin Wiles, no worries, the name doesn't need to be unique across all instances of the resource, but the tuple of all of the namevars does. The tuple is what puppet refers to the uniqueness key in https://github.com/puppetlabs/puppet/blob/5.4.0/lib/puppet/type.rb#L432-L439. There are a few different rules for how puppet determines which parameters are namevars, see https://github.com/puppetlabs/puppet-specifications/blob/master/language/resource_types.md#namevar. When using composite namevars you must provide title_patterns to map the composite title back into its constituent namevars, see https://github.com/puppetlabs/puppet-specifications/blob/master/language/resource_types.md#title-patterns. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-328) Don't pass task paths to run_task
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-328 Don't pass task paths to run_task Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8425) Prepare Confluence and JIRA for release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8425 Prepare Confluence and JIRA for release (Puppet Platform 5.4.0) Change By: Kenn Hussey Summary: Prepare Confluence and JIRA for release (Puppet Platform 5.4.0) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8425) Prepare JIRA for release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8425 Prepare JIRA for release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed as are those that we intend to ship with the release.2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.4) Update the “master” filters for Puppet Platform 5.4.0 and puppet-agent 5.4.0 to reference the “Fixed in” filters created above.5) Update the community feedback filter for Puppet Platform 5.y to reference the “Introduced in” filter created above. Add Comment This message was sent by
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Maggie Dreyer commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Jacob Helwig would you mind looking into if this still applies? I think there is an epic around improving failure reporting in Puppet somewhere that this might fit into. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Maggie Dreyer Labels: needs_repo needs_repro Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3557 Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3309) puppet master --compile should be able to source facts from master inventory service
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3309 puppet master --compile should be able to source facts from master inventory service Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title
Alex Dreyer commented on BOLT-337
Re: Nodes in inventory groups should accept "host:port" syntax
There are some complex questions about identity of `Targets` we've been putting off answering that will be an issue once we start handling facts and data. The shortcoming we seem to have now is that name in inventory is "hostname" and there is no way to have two entries with the same hostname. I can think of two non-exclusive solutions for this problem. 1. Name/Identity can be full uris.
nodes:
- name: node1
confport:
- node1:
- node1:2224
Facts and data for get_targets('node1') and get_targets('node1:22') are separate. 2. Hostname can be set separately from name/identity.
nodes:
-node1
port:
- container1
host: node1
port:
Jira (PUP-8464) puppet help should process its arguments better
Title: Message Title Eric Delaney created an issue Puppet / PUP-8464 puppet help should process its arguments better Issue Type: Task Assignee: Eric Delaney Created: 2018/02/14 10:30 AM Priority: Normal Reporter: Eric Delaney The puppet help face should do a better job of processing its arguments and giving useful user error messages: $ bx puppet help agent thing Error: Legacy subcommands don't take actions Error: Try 'puppet help help help' for usage $
Jira (PUP-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Garrett Guillotte commented on PUP-8427 Re: Prepare release announcement (Puppet Platform 5.4.0) CC Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8021) Puppet needs to support all FIPS approved hash algs
Title: Message Title Jayant Sane updated an issue Puppet / PUP-8021 Puppet needs to support all FIPS approved hash algs Change By: Jayant Sane Release Notes Summary: Puppet now supports SHA 224, 256, 384, 512 hash algorithms for file checksums and digital signatures . Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-2844) Puppet sends warnings and errors to stdout
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-2844 Puppet sends warnings and errors to stdout Change By: Maggie Dreyer Summary: "puppetmasterd --compile" Puppet sends extraneous messages warnings and errors to stdout Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-2844) Puppet sends warnings and errors to stdout
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-2844 Puppet sends warnings and errors to stdout Change By: Maggie Dreyer Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Garrett Guillotte commented on PUP-8427 Re: Prepare release announcement (Puppet Platform 5.4.0) Puppet Platform 5.4.0 is a feature release that adds agent support for FIPS-compliant platforms, improves filebucket handling, improves several Puppet language features and adds new functions and types, improves PuppetDB performance, and adds new profiling features to Puppet Server. For details, see the release notes for [Puppet agent 5.4.0](https://puppet.com/docs/puppet/5.4/release_notes_agent.html), [Puppet Server 5.2.0](https://puppet.com/docs/puppetserver/5.2/release_notes.html), and [PuppetDB 5.2.0](https://puppet.com/docs/puppetdb/5.2/release_notes.html). Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Garrett Guillotte assigned an issue to Molly Waggett Puppet / PUP-8427 Prepare release announcement (Puppet Platform 5.4.0) Change By: Garrett Guillotte Assignee: Molly Waggett Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-3138) improve spec functions "produces" and "fails" in language.rb
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-3138 improve spec functions "produces" and "fails" in language.rb Change By: Maggie Dreyer Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8442) type parameters do not honor when default is set to false
Title: Message Title Eric Delaney commented on PUP-8442 Re: type parameters do not honor when default is set to false Merged to master at https://github.com/puppetlabs/puppet/commit/1b2969e2654520484ed7918675a7b7b38b32ee7b Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-337
Nodes in inventory groups should accept "host:port" syntax
Change By:
Alex Dreyer
Environment:
When trying to use inventory files with docker containers, we ran into problems using this kind of syntax to address hosts. Each container has a different port that ssh is running on, but syntax like this didn't work:{code:yaml}groups: - name: labnodes:- node1:32768- node2:32769- node3:32770{code}Instead this, much less untuitive syntax, was necessary:{code:yaml}groups: - name: labnodes: - node1 - node2 - node3config: transport: ssh transports:ssh: host-key-check: falsehosts: - host: node1config: transport:ssh: port: 32768 - host: node2config: transport:ssh: port: 32769 - host: node3config: transport:ssh: 32770{code}Feels like that first option ought to work.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
--
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 (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-337
Nodes in inventory groups should accept "host:port" syntax
Change By:
Alex Dreyer
When trying to use inventory files with docker containers, we ran into problems using this kind of syntax to address hosts. Each container has a different port that ssh is running on, but syntax like this didn't work:{code:yaml}groups: - name: labnodes:- node1:32768- node2:32769- node3:32770{code}Instead this, much less untuitive syntax, was necessary:{code:yaml}groups: - name: labnodes: - node1 - node2 - node3config: transport: ssh transports:ssh: host-key-check: falsehosts: - host: node1config: transport:ssh: port: 32768 - host: node2config: transport:ssh: port: 32769 - host: node3config: transport:ssh: 32770{code}Feels like that first option ought to work.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8419) Agent's node request fails if environment directory doesn't exist locally
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8419 Agent's node request fails if environment directory doesn't exist locally Change By: Kenn Hussey Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-332) Target objects should store state of the Targets
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-332
Target objects should store state of the Targets
Change By:
Michael Smith
Plan authors should be able to store data (called 'vars' for now) on the Target objects and retrieve it during a plan.Changes:- Inventory should track all target instances created(at least with get_target {{get_targets}} ) and return the same instance every time get_target {{get_targets}} is called.- There should be a puppet function set_var(Target $target, String $key, Data $value) that sets the value in vars in a way that works even if the Target was created outside get_target- Target.vars should return vars as a Hash- vars should be settable in the inventory file at the same level as config. When a target is created the merged value of all vars from the inventory file should be included (deep merge hashes, choose the first for other values).We expect this to be the first ticket in an arc of node data that will include, gathering and storing facts on targets, assigning per target task parameters and using target facts and vars to perform target specific hiera lookups
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8430) Update Confluence and JIRA based on release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8430 Update Confluence and JIRA based on release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages under the appropriate parent pages under “Current Releases”.2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”.3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates.4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date.5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers.6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers.7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description and release date of each version as needed based on what was shipped when. Add Comment
Jira (BOLT-332) Target objects should store state of the Targets
Title: Message Title
Alex Dreyer commented on BOLT-332
Re: Target objects should store state of the Targets
We have a `Target` datatype that is returned by `get_targets` already. Our plan is to add `set_var` and `vars` onto the datatype. In practice this is what we want
$t1 = get_target('mynode)
$t2 = get_target('mynode')
# to a lesser extent $t3 = Target('mynode')
$t1.set_var('foo', 10)
assert($t2.vars['foo'] == 10)
Wether that is accomplished by get_target returning the same instance and set_var mutating the instance or set_var/vars accessing global state doesn't seem particularly important. I would not expect 'mynode'.set_var(foo, 10) to work. Not specifically target related: Why must values be immutable in the plan language? In order to resolve the references in a declarative catalog permanent binding and immutable values make sense but during plan execution it doesn't seem as valuable. For a plan language to attracts non-puppet users I think we need to accept some level of mutability. I've written a lot of clojure and prolog and it's still annoying for me.
$result = {}
$result = $result.set('first_run', run_task('foo', $nodes))
$nodes.each |$n| {
$result = $result.merge("$node_run" => run_task('bar', $n))
Jira (BOLT-337) Nodes in inventory groups should accept "host:port" syntax
Title: Message Title Eric Sorenson created an issue Puppet Task Runner / BOLT-337 Nodes in inventory groups should accept "host:port" syntax Issue Type: Bug Assignee: Unassigned Created: 2018/02/14 9:51 AM Environment: When trying to use inventory files with docker containers, we ran into problems using this kind of syntax to address hosts. Each container has a different port that ssh is running on, but syntax like this didn't work: groups: - name: lab nodes: - node1:32768 - node2:32769 - node3:32770 Instead this, much less untuitive syntax, was necessary: groups: - name: lab
Jira (BOLT-318) I want to refer to inventory groups as targets
Title: Message Title Eric Sorenson commented on BOLT-318 Re: I want to refer to inventory groups as targets In working through this feature with the CS team yesterday, nearly everyone expected that a bareword argument to -nodes that matched a group name would target that group, and if there were no matches it would be treated as a hostname. Additional syntax could be used to disambiguate but the group thought if so, it should be some punctuation sigil, by analogy to the -nodes @file syntax to indicate loading from a file. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-198) Add 'bolt task show' instructions to error message for incorrect task
Title: Message Title Kate Lopresti commented on BOLT-198 Re: Add 'bolt task show' instructions to error message for incorrect task I think I understand the error message constraints better now: 1 line with a filepath appended to the end. Could not find a task named "foo::fail1" For a list of available tasks, run "bolt task show" (file: /Users/michaelsmith/puppetlabs/bolt/tmp/foo/plans/fail.pp, line: 5) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-336) Treat --nodes as the node parameter for run plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-336 Treat --nodes as the node parameter for run plan Issue Type: New Feature Assignee: Unassigned Created: 2018/02/14 9:35 AM Priority: Normal Reporter: Alex Dreyer Many plans take a nodes argument but when users switch from running a task/command/script on those nodes and running a plan on them they have to remember to strip '--' from nodes. To prevent this bolt should treat --nodes as the value of the nodes parameter for run plan. If both --nodes and nodes= are specified bolt should error If multiple --nodes are specified bolt should concatentate them like it does for run task. If --nodes is passed to a plan that doesn't have a node parameter bolt should error. --nodes should not be converted to targets outside the plan Add Comment
Jira (PUP-8425) Prepare JIRA for release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8425 Prepare JIRA for release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed as those that we intend to ship with the release.2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.4) Update the “master” filters for Puppet Platform 5.4.0 and puppet-agent 5.4.0 to reference the “Fixed in” filters created above.5) Update the community feedback filter for Puppet Platform 5.y to reference the “Introduced in” filters filter created above. Add Comment This message was sent
Jira (PUP-8425) Prepare JIRA for release (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8425 Prepare JIRA for release (Puppet Platform 5.4.0) Change By: Kenn Hussey (Initial planned release date: 2018-02-13)1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed as those that we intend to ship with the release.2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA.3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it.4) Update the “master” filters for Puppet Platform 5.4.0 and puppet-agent 5.4.0 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform 5.y to reference the “Introduced in” filters created above. Add Comment This message was sent by
Jira (PUP-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Kenn Hussey commented on PUP-8427 Re: Prepare release announcement (Puppet Platform 5.4.0) Garrett Guillotte is this ready to go? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-323) Add tests for --run-as as a non-root user
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-323 Add tests for --run-as as a non-root user Change By: Lucy Wyman Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-8463) Remove existing warnings and run PRs through 'ruby -wc'
Title: Message Title Jacob Helwig created an issue Puppet / PUP-8463 Remove existing warnings and run PRs through 'ruby -wc' Issue Type: Task Assignee: Jacob Helwig Created: 2018/02/14 8:23 AM Fix Versions: PUP Future Priority: Normal Reporter: Jacob Helwig Puppet currently has a large number of Ruby warnings that should be cleaned up as some of them are causing actual bugs. How to find all of the Ruby warnings in the Puppet repo (this will be slow): find lib spec -type f -name \*.rb | xargs -n1 ruby -wc > /dev/null After all of the warnings have been removed, we should update Travis CI to run any Ruby file changed in a PR through "ruby -wc" to make sure that we don't reintroduce any warnings (or potential bugs that would have been caught by the warnings).
Jira (BOLT-332) Target objects should store state of the Targets
Title: Message Title Henrik Lindberg commented on BOLT-332 Re: Target objects should store state of the Targets I missed that the description had been updated. What is proposed there looks like there needs to be a data type for the target instance unless get_target returns a generic hash of the target information. The function get_target could then also accept the "dot notation" to allow navigation, and thus return som arbitrary current value. That would avoid having to create a copy of all vars to return (to make sure all returned values are immutable). Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-332) Target objects should store state of the Targets
Title: Message Title Henrik Lindberg commented on BOLT-332 Re: Target objects should store state of the Targets Alex Dreyer part of your last comment seems to be missing as it ends with "Another example might be". Anyway... In whatever is done I think it is important to differentiate between a reference to a target and an instance that represents the target's state. A big mistake in the puppet code base where this was not done is in the implementation of Resource as it serves as a reference when it only has a type/title, and serves as a resource state when filled in - that effectively prevents any validation to be done (for instance wrt required values). Internally that also led to lots of casting back and forth between an external representation (a string) and a Resource instance. I am saying this because I think creating a similar construct to that is to be avoided. (That is the reason why the data type Resource is a reference to a resource and not the data type for the resource instances - thus if you were to create an instance of that data type, you would create a new reference - in the language resource instances are created by a resource _expression_ or by calling create_resources - those instances are however never available as values in the puppet language. If the idea for Target is similar (it is a reference, and instances are created via other means) but where the instances are available, then they must have a data type. URI is a very handy generic reference, but a decision was made to use Target as a specialized reference in order to find those parameters when introspecting a Plan. You say that values associated with targets are to be available for the duration of the plan. Does that mean that they go back to what they were a plan goes out of scope? A plan may call other plans for instance. Or do you mean that they stay the same from when they are changed until the target instance goes out of scope? Yet another thing to consider is that puppet language requires values to be immutable. Whatever is obtained from a target instance - say calling a_target.facts must return something immutable - i.e. a copy of the facts - since it is wanted to be able to change the value of the target's set of facts (or individual facts). That can be expensive, and thus a target instance should have methods that allows getting individual facts. (See discussion regarding the get() function for something similar). Hope this makes some sense... Add Comment
Jira (PUP-7822) Add a get() function that supports dot syntax to "dig" into hash/array
Title: Message Title
Henrik Lindberg commented on PUP-7822
Re: Add a get() function that supports dot syntax to "dig" into hash/array
The reason I am not keen on that solution is that get('varname') is a dynamic way to access a variable akin to Scope#get_var in Ruby. In Ruby that is needed since puppet variables simply has to be fetched using a method as they are not "ruby variables". Using indirection like that has been frowned upon in the past and thus the reason why the puppet language does not have a way to get a variable value given a string variable name. OTOH - we now have a call() function that can call a named function. This means you could write a function each for each variable you want to access (function only returns that variable) and then you select the function to call in place of directly selecting a variable name. Not saying that is a solution here, just pointing out that it is possible to do this now in puppet language alone in a very cumbersome way. (You could naturally write your own "getvar" in Ruby to return any variable). So, while I am not "keen", I am also not absolutely opposed to the idea. Here are some of the questions the idea raises:
Would get('varname') behave the same as just $varname - i.e. it would error/warn if the variable does not exist as controlled by strict_variables setting?
Or, should it behave more in the style of "dot-notation" and return undef if variable does not exist? (with or without warning, controlled by strict_variables or not?).
Can it be used with fully qualified names like get('mymodule::mything::innerthing')? Does get('varname') work from topscope only - i.e. get('::varname') is implied?
Or should it support resolution of variable name against local scope and users must use leading :: to indicate topscope to avoid picking variable in local scope?
The rest of the "dot-notation" string is what it already is - nothing special there.
Add Comment
