Jira (PUP-8898) Change default input_method for Task object type
Title: Message Title Jacob Helwig commented on PUP-8898 Re: Change default input_method for Task object type Merged to master branch in puppet in 5f919012f2. 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-8898) Change default input_method for Task object type
Title: Message Title Jacob Helwig assigned an issue to Cas Donoghue Puppet / PUP-8898 Change default input_method for Task object type Change By: Jacob Helwig Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-503
Use local config automatically to embed bolt in a project
Change By:
Alex Dreyer
I want to use bolt as a tool to manage my applications including everything needed with the application repo itself.Currently this is possible by including {{bolt.yaml}} at the top level of your project, in {{bolt.yaml}} point to a modules an inventory inside the project repo. But then every command needs to be run with {{--config=$PROJECT_PATH/bolt.yaml}}.Solutions:When bolt runs it should search the {{cwd}} and its ancestors for a directory called {{Boltdir}}. If one is found the bolt should run in Boltdir mode where default location for {{bolt.yaml}}, {{inventory.yaml}} should be at the top level of the Boltdir and the modulepath should default to {{ [ Boltdir/modules/ ] }}The global config and inventory should not be loaded by default when running in Boltdir mode.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
Jira (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-503
Use local config automatically to embed bolt in a project
Change By:
Alex Dreyer
I want to use bolt as a tool to manage my applications including everything needed with the application repo itself.Currently this is possible by including {{bolt.yaml}} at the top level of your project, in {{bolt.yaml}} point to a modules an inventory inside the project repo. But then every command needs to be run with {{--config=$PROJECT_PATH/bolt.yaml}}.Solutions:When bolt runs it should search the {{cwd}} and its ancestors for a directory called {{Boltdir}}. If one is found the bolt should run in Boltdir mode where default location for {{bolt.yaml}}, {{inventory.yaml}} should be at the top level of the Boltdir and the modulepath should default to {{[ Boltdir/modules/ ]}} Users should be able to specify the boltdir from the commandline with {{--boltdir}}. The global config and inventory should not be loaded by default when running in Boltdir mode.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-555) Accept 'tty' option in inventory and/or config file
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-555 Accept 'tty' option in inventory and/or config file Issue Type: Improvement Assignee: Unassigned Created: 2018/05/30 2:53 PM Priority: Normal Reporter: Michael Smith Currently 'tty' is a CLI-only option. Allow it to be configured in inventory and/or config files. First filed as https://github.com/puppetlabs/bolt/issues/453. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8588) Support multiple implementations when loading tasks
Title: Message Title Michael Smith updated an issue Puppet / PUP-8588 Support multiple implementations when loading tasks Change By: Michael Smith Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Michael Smith 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 (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask Change By: Lucy Wyman Release Notes Summary: This adds the ability to install bolt on OSX systems using `brew cask install puppetlabs/puppet/puppet-bolt 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 (BOLT-549) Bolt Script Run not supported for AIX
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-549 Bolt Script Run not supported for AIX Change By: Michael Smith Fix Version/s: BOLT-546 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-465) Publish Bolt to Homebrew Cask
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask 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 (BOLT-494) Document how to opt-out of analytics
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-494 Document how to opt-out of analytics 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 (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms 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 (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project 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 (BOLT-521) I want to escalate with a non-sudo command
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command 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 (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title Lucy Wyman assigned an issue to Unassigned Puppet Task Runner / BOLT-465 Publish Bolt to Homebrew Cask Change By: Lucy Wyman Assignee: Lucy Wyman 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 (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker updated an issue Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Change By: Nick Walker CS Priority: Needs Priority 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 (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker updated an issue Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Change By: Nick Walker h1. The ProblemWe came out with structured facts or "modern facts" as we call them long ago, however, we still have legacy facts and we send both the legacy version and the modern version whenever the agent requests a catalog. This means we are allowing users to refer to the legacy fact names in code and potentially creating tech debt if we ever remove the legacy fact names, as we probably should. Additionally we are burdening PuppetDB with all of the duplicate information since legacy facts are represented in the modern facts. Downstream of PuppetDB the PE Console is slowed down by the large amount of unique fact names caused by legacy facts. h1. Suggested Improvement We should provide an option to disable legacy facts altogether so that the agent doesn't send them to the master and then subsequently they do not get stored in PuppetDB. We could provide this as an option, deprecate legacy facts and remove them in a future version. h1. Side thoughtGiven this type of setting it could be plumbed into spec testing so that legacy facts could be disabled and tests could fail if someone refers to a legacy fact name. This would give early warning to users. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Nick Walker created an issue Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Issue Type: Improvement Assignee: Unassigned Created: 2018/05/30 1:50 PM Priority: Normal Reporter: Nick Walker The Problem We came out with structured facts or "modern facts" as we call them long ago, however, we still have legacy facts and we send both the legacy version and the modern version whenever the agent requests a catalog. This means we are allowing users to refer to the legacy fact names in code and potentially creating tech debt if we ever remove the legacy fact names, as we probably should. Additionally we are burdening PuppetDB with all of the duplicate information since legacy facts are represented in the modern facts. Downstream of PuppetDB the PE Console is slowed down by the large amount of unique fact names caused by legacy facts. Suggested Improvement We should provide an option to disable legacy facts altogether so that the agent doesn't send them to the master and then subsequently they do not get stored in PuppetDB. We could provide this as an option, deprecate legacy facts and remove them in a future version. Add Comment
Jira (PDB-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Adam Bottchen CS Priority: Needs Priority 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-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Change By: Rob Browning Team: Data Platform Sprint: Hopper/Triage 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-543) Automate updating the version and sha of brew package
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-543 Automate updating the version and sha of brew package Change By: Lucy Wyman The current bolt brew package lives at https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb, where the version is hard coded. We currently need to manually update this and the SHAs on release. This should be part of our release pipeline https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ . Automation should live in ci-job-configs, and should be general enough that the PDK team (and other teams) can also use it to update the same 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
Jira (BOLT-543) Automate updating the version and sha of brew package
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-543 Automate updating the version and sha of brew package Change By: Lucy Wyman The current bolt brew package lives at https://github.com/ Homebrew puppetlabs /homebrew- cask puppet /blob/master/Casks/puppet-bolt.rb, and has where the version set to 'latest' and is set to not check the sha hard coded . This is fine for now, but eventually we'll want We currently need to have the specific version manually update this and sha in that file the SHAs on release . This means the new workflow will should be to update that file and create a PR against part of our release pipeline https:// github jenkins-master-prod-1 . com delivery.puppetlabs.net / Homebrew view / homebrew bolt/job/platform_bolt - cask, which we want to be an automated part of our CI vanagon_bolt- release pipeline. This automation should be generalized so the pdk team can also take advantage of it. -init_bolt-release/ Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-465) Publish Bolt to Homebrew Cask
Title: Message Title Lucy Wyman commented on BOLT-465 Re: Publish Bolt to Homebrew Cask This lives at https://github.com/puppetlabs/homebrew-puppet , along with install instructions. Updating the version on release is necessary, and is not currently automated but should be in the future – see BOLT-543. 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-399) Update fact gathering task to leverage cross-platform support
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-399 Update fact gathering task to leverage cross-platform support 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 (PDB-3928) Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern
Title: Message Title Nick Walker created an issue PuppetDB / PDB-3928 Facts blacklist should support providing a fact name regex to blacklist facts matching a pattern Issue Type: Improvement Assignee: Unassigned Created: 2018/05/30 1:31 PM Priority: Normal Reporter: Nick Walker The Problem The puppet agent still sends legacy facts to the puppet master and they are forwarded onto PuppetDB. However, there's not many good reasons to store the legacy facts in addition to the modern structured facts. Take a look at the list of legacy facts here: https://puppet.com/docs/facter/3.9/core_facts.html Notice that alot of them include a network interface or something else unique which is bloating PuppetDB's fact storage full of unique facts. This makes lists of facts for populating things like autocomplete in the console UI larger and slower than they need to be. Suggested Improvement We already have a facts-blacklist in PuppetDB which could be used to workaround this problem if it allowed for a regex match on fact name so we could exclude facts like `mtu_` or `blockdevice_` https://puppet.com/docs/puppetdb/5.1/configure.html#facts-blacklist This isn't a full solution, really we should either stop sending legacy facts from the agent to the mater OR stop forwarding legacy facts from the master onto PuppetDB. Since those may have unintended consequences or may just be a breaking change, this improvement allows customers that want to take the initiative a way to remove these facts from being stored in PuppetDB.
Jira (BOLT-550) Bolt 0.20.4 2018-05-31 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-550 Bolt 0.20.4 2018-05-31 Release Change By: Lucy Wyman Sprint: Bolt 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 (BOLT-551) Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-551 Reconcile git commits, JIRA tickets, and versions (Bolt 0.20.4) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2018/05/30 1:16 PM Due Date: 2018/05/31 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-05-31) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-552) Kick off release pipeline (Bolt 0.20.4)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-552 Kick off release pipeline (Bolt 0.20.4) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2018/05/30 1:16 PM Due Date: 2018/05/31 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-05-31) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-399) Update fact gathering task to leverage cross-platform support
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-399 Update fact gathering task to leverage cross-platform support 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 (BOLT-554) Send release announcements (Bolt 0.20.4)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-554 Send release announcements (Bolt 0.20.4) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/05/30 1:16 PM Due Date: 2018/05/31 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-05-31) Once docs have finished building (check that all links resolve appropriately) - Send the announcement pasted by Kate Lopresti to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and d...@puppet.com (all separately). You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 0.20.4 is now available". Add Comment
Jira (BOLT-553) Docs for bolt release (Bolt 0.20.4)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-553 Docs for bolt release (Bolt 0.20.4) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/05/30 1:16 PM Due Date: 2018/05/31 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-05-31) Release notes and docs changes for bolt 0.20.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-550) Bolt 0.20.4 2018-05-31 Release
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-550 Bolt 0.20.4 2018-05-31 Release Issue Type: Task Assignee: Cas Donoghue Created: 2018/05/30 1:16 PM Priority: Normal Reporter: Lucy Wyman Bolt 0.20.4 2018-05-31 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-135) I want to execute different versions of the task file on different platforms
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-135 I want to execute different versions of the task file on different platforms Change By: Michael Smith Assignee: Michael Smith 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-546) mktemp is not available on all platform (AIX specifically)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-546 mktemp is not available on all platform (AIX specifically) Change By: Michael Smith Sprint: Bolt Ready for 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-8898) Change default input_method for Task object type
Title: Message Title Michael Smith updated an issue Puppet / PUP-8898 Change default input_method for Task object type Change By: Michael Smith Sub-team: Bolt Team: Direct Change Sprint: Bolt 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-8696) Puppet loses track of the current environment
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8696 Puppet loses track of the current environment Change By: Josh Cooper Acceptance Criteria: Puppet agent should never load types/providers from its modulepath, instead always loading them from its libdir (since it needs to use the same version of modules as the compiler used to generate the catalog).Puppet should continue to be able to load applications from modules. There is an acceptance test for this already.Puppet should always load features from the current environment. Previously it used the configured environment (so the agent could load the feature from a locally installed module, instead of what it pluginsynced). 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-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Story Points: 3 1 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-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Sprint: Windows 2018-05-30, Windows 2018-06- 13 06 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-8582) Add vendor_modules to basemodulepath
Title: Message Title Melissa Stone commented on PUP-8582 Re: Add vendor_modules to basemodulepath Merged into master with 77b29c66219be28a6594c013146e1e15edbf3d01 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-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Acceptance Criteria: When running puppetserver, the server should be able to compile a catalog when the manifest contains a resource whose type/provider is in the server's vendored module path, e.g. mailalias.When running puppetserver, if a new version of a module is installed on the server, e.g. puppet module install, the server should prefer that over the vendored version.When running puppet agent, the agent should always pluginsync and use the same version of type/provider as was used to compile the catalog, even if the agent has a local vendored version. Note this behavior is broken until PUP-8696 is resolved.When running puppet apply/describe/resource/etc, puppet should prefer its vendored modules over whatever it pluginsynced.When running puppet apply/describe/resource/etc, if a new version is installed on the local host, then puppet should prefer that over vendored versions. If the basemodulepath setting is set of $codedir/modules, then puppet should ignore vendored modules for server, agent, apply, etc. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received
Jira (PUP-8582) Add vendor_modules to basemodulepath
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8582 Add vendor_modules to basemodulepath Change By: Josh Cooper Acceptance Criteria: When running puppetserver, the server should be able to compile a catalog when the manifest contains a resource whose type/provider is in the server's vendored module path, e.g. mailalias.When running puppetserver, if a new version of a module is installed on the server, e.g. puppet module install, the server should prefer that over the vendored version.When running puppet agent, the agent should always pluginsync and use the same version of type/provider as was used to compile the catalog, even if the agent has a local vendored version. Note this behavior is broken until PUP-8696 is resolved.When running puppet apply/describe/resource/etc, puppet should prefer its vendored modules over whatever it pluginsynced.When running puppet apply/describe/resource/etc, if a new version is installed on the local host, then puppet should prefer that over vendored versions. 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
Jira (PUP-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Sprint: Windows 2018-05-30, Windows 2018-06- 06 13 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-4684) windows file resource doesn't grant group full permissions
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4684 windows file resource doesn't grant group full permissions Change By: Craig Gomes Sprint: Windows 2018-05-30 , Windows 2018-06-06 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-8771) Write integration/acceptance tests for NTFS permissions for PUP-6729
Title: Message Title Craig Gomes updated an issue Puppet / PUP-8771 Write integration/acceptance tests for NTFS permissions for PUP-6729 Change By: Craig Gomes Sprint: Windows 2018-05-30 , Windows 2018-06-06 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-8762) deprecate `puppet module build` in favor of `pdk build`
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8762 deprecate `puppet module build` in favor of `pdk build` Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.3 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-8762) deprecate `puppet module build` in favor of `pdk build`
Title: Message Title Josh Cooper commented on PUP-8762 Re: deprecate `puppet module build` in favor of `pdk build` Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/e79060ee874c3e69233257917b8334b10eb575da 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-521) I want to escalate with a non-sudo command
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command 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-8773) Logging as JSON broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8773 Logging as JSON broken Change By: Josh Cooper Release Notes Summary: The introduction of multi_json in 5.5.0 broke the JSON log destination. This fixes the regression. 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 (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project Change By: David Kramer Assignee: Alex Dreyer 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-521) I want to escalate with a non-sudo command
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-521 I want to escalate with a non-sudo command Change By: Alex Dreyer Release Notes Summary: Bolt now allows you to specify the command to use when escalating privileges over ssh 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-8773) Logging as JSON broken
Title: Message Title Josh Cooper commented on PUP-8773 Re: Logging as JSON broken Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/05ebba88c96ea3cb14a2a4c00387e10ae1701dc4 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-534 Request for ability to run tasks with escalated privileges in non interactive mode Change By: Alex Dreyer Issue Type: New Feature Bug 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-534) Bolt hangs when no sudo password is provided.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-534 Bolt hangs when no sudo password is provided. Change By: Alex Dreyer Summary: Request for ability to run tasks with escalated privileges in non interactive mode Bolt hangs when no sudo password is provided. 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-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Alex Dreyer commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode Can you add more specifics about the environment in which this is happening and the inputs to bolt you're using. I'm going to convert this issue to a bug. 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-534) Bolt hangs when no sudo password is provided
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-534 Bolt hangs when no sudo password is provided Change By: Alex Dreyer Summary: Bolt hangs when no sudo password is provided . 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-8773) Logging as JSON broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8773 Logging as JSON broken Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8585 puppet device --resource should fail if non-existent target is given Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.3 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-8735) File resource doesn't seem to parse UTF8 filenames when recursively copying directories
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8735 File resource doesn't seem to parse UTF8 filenames when recursively copying directories Change By: Josh Cooper Fix Version/s: PUP 5.5.x Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8585 puppet device --resource should fail if non-existent target is given Change By: Josh Cooper Fix Version/s: PUP 5.5.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8585) puppet device --resource should fail if non-existent target is given
Title: Message Title Josh Cooper commented on PUP-8585 Re: puppet device --resource should fail if non-existent target is given Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/f4f375c66848e7b3a7d1146394e21f34ea628d6f 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 (FACT-1857) Error lauching puppet agent
Title: Message Title Bastien CACCIUTTOLO created an issue Facter / FACT-1857 Error lauching puppet agent Issue Type: CI Blocker Assignee: Unassigned Created: 2018/05/30 7:52 AM Environment: Red Hat 6.9 Puppet version 3.8.6 Facter version 1.7.5 Priority: Normal Reporter: Bastien CACCIUTTOLO Hi, When I want to launch my puppet agent, I get an error which stops the execution of the command : Error : Could not retrieve local facts: unintialized constant Facter::Core Error : failed to apply catalog: Could not retrieve local facts: unintialized constant Facter::Core I try to solve this problem for a few days now but I can't find any relevant information on the net and I don't know how to solve it. Can you help me or at least show me a path to look for. Thanks, Kind regards. Add Comment
Jira (PUP-8774) puppet device does not use locking
Title: Message Title Thomas Honey commented on PUP-8774 Re: puppet device does not use locking Hi Bas Toonk i am just following up with this, due to some of the functionality in device locking the process does not make sense. However i could see this being added as a possible new feature. IE opting into process locking. This would not be a priority, currently. Thanks for taking the time to document this. 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-8899) New setting to allow external control over start of puppet run
Title: Message Title Matthias Hörmann created an issue Puppet / PUP-8899 New setting to allow external control over start of puppet run Issue Type: New Feature Assignee: Unassigned Created: 2018/05/30 2:51 AM Priority: Normal Reporter: Matthias Hörmann 5.5.1 on Linux We have a host system with many containers, all managed by Puppet. When the hosts boots or all containers need to be restarted for some reason, all Puppet agents start at the same time. We do not want to use splay since that would affect Puppet restarts we perform manually after changing configuration. It would be useful if Puppet had some sort of setting, similar to pre_run_command and post_run_command to allow an external script to decide whether a Puppet run should start now. I imagine this to work as a polling mechanism, where Puppet polls an external script repeatedly for permission to run now after its own runinterval has expired. I do not want to implement this via pre_run_command since i do not think this is designed for arbitrary wait intervals. This could solve our problem by allowing us to implement our own worker pool logic in e.g. a shared directory, where a Puppet agent needs to lock one of a limited number of slots before it can start its run. We could then free that slot again in post_run_command. Add Comment
Jira (BOLT-549) Bolt Script Run not supported for AIX
Title: Message Title Vinoth Kumar created an issue Puppet Task Runner / BOLT-549 Bolt Script Run not supported for AIX Issue Type: Bug Affects Versions: BOLT 0.19.1 Assignee: Unassigned Components: Errors Created: 2018/05/30 1:56 AM Environment: All AIX Operating systems Labels: Engineering-Initiative Priority: Normal Reporter: Vinoth Kumar Bolt script run fails for AIX Servers stating " Could not make tempdir: ksh: mktemp: not found." AIX Doesn't support mktemp command, Please help to change it to mkdir -p /tmp or similar command Add Comment
Jira (BOLT-534) Request for ability to run tasks with escalated privileges in non interactive mode
Title: Message Title Eoin McQuillan commented on BOLT-534 Re: Request for ability to run tasks with escalated privileges in non interactive mode Hi Alex - the behaviour I am seeing is it is just hanging there. 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.
