Jira (PUP-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title John Duarte commented on PUP-9652 Re: Delete acceptance tests with 'audit:delete' tag Rob Braden, I don't know what the current process is to get this in front of the Coremunity team, but the PR is available for review. 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-9652) Delete acceptance tests with 'audit:delete' tag
Title: Message Title John Duarte commented on PUP-9652 Re: Delete acceptance tests with 'audit:delete' tag PR 7496 opened to delete these tests. 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-1269) Prompt for sensitive data from inventory.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1269
Prompt for sensitive data from inventory.
Change By:
Alex Dreyer
In scope:* Have a single generalized inventory plugin hook.* allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered.* implement a prompt plugin that accepts a single {{name}} parameter.* Do not prompt until something to {{update_target}} for a target which needs this information. Out of scope: * worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars) * making a decision on whether target-lookups are special.{noformat}nodes: - uri: my_node config: ssh: password: { _plugin: prompt, message: "Password for my_node"}dgroups: - name: first_grouptargets: [ ]config: ssh: password: _plugin: prompt message: "Password for first group"{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1269
Prompt for sensitive data from inventory.
Change By:
Alex Dreyer
In scope:* Have a single generalized inventory plugin hook.* allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered.* implement a prompt plugin that accepts a single {{name}} parameter.* Do not prompt until something to {{update_target}} for a target which needs this information. Out of scope:worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars)making a decision on whether target-lookups are special.{ { noformat} } nodes: - uri: my_node config: ssh: password: { _plugin: prompt, message: "Password for my_node"}dgroups: - name: first_grouptargets: [ ]config: ssh: password: _plugin: prompt message: "Password for first group"{ { noformat} }
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1269
Prompt for sensitive data from inventory.
Change By:
Alex Dreyer
In scope: * Have a single generalized inventory plugin hook. * allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered. * implement a prompt plugin that accepts a single {{name}} parameter. support lazily evaluating the " * Do not prompt plugin" when fetching config until something to {{update_target}} for a node or group target which needs this information . Out of scope:worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars)making a decision on whether target-lookups are special.{{noformat}} nodes: - uri: my_node config: ssh: password: { _plugin: prompt, message: "Password for my_node"}d groups: - name: first_grouptargets: [ ]config: ssh: password: _plugin: prompt message: "Password for first group pass " {{ nofrmat noformat }}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1269
Prompt for sensitive data from inventory.
Change By:
Alex Dreyer
In scope:Have a single generalized inventory plugin hook.allow plugins to be used at arbitrary locations in inventory whenever an object with a {{_plugin}} key is encountered.implement a prompt plugin that accepts a single {{name}} parameter.support lazily evaluating the "prompt plugin" when fetching config for a node or group.Out of scope:worrying about inventory plugins outside of config.(ie for names, targets, facts, or vars)making a decision on whether target-lookups are special.{{noformat}}groups: - name: first_grouptargets: [ ]config: ssh: password: _plugin: prompt message: "Password for group pass {{nofrmat}}
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 thi
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Thomas Kishel commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Jean Bond The release notes I suggested have been replaced with the release notes for PUP-9565 ? 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-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1265
target-lookup plugin to discover targets from a terraform state file.
Change By:
Lucy Wyman
Questions:- How will the user specify where the statefile is? Is this config for the plugin or part of the lookup?- How will the user specify the name of the target?- How will the user specify connection info(host)? Plugin configuration?- Is there anything we can do that is terraform specific?At least try shelling out to `tf state` - if it's not available fail. State server on it's own is not supported.Need to have the terraform project directory path, and a second optional path to the statefile itself if you have multiple.Should be passed as a parameter to the lookup, as opposed to a way of configuring the lookup Solution:{code}{resource_type: resources.gce_instance.*uri: network.public_ipconfig: ssh:hostname: id}{code}So you specify a resource_type which is the "scope" in terraform where your resource exists, specified in the terraform-dot-syntax. Below that you specify bolt config, where each config option accepts a terraform-dot-syntax scope for looking up fields in the top level syntax. Ideally this will also accept regexes.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9686) Allow initializing Puppet w/o loading Facter
Title: Message Title Justin Stoller created an issue Puppet / PUP-9686 Allow initializing Puppet w/o loading Facter Issue Type: Improvement Assignee: Unassigned Created: 2019/04/25 2:33 PM Priority: Normal Reporter: Justin Stoller It is desirable that Puppet server load and initialize Puppet (including the constant Puppet) w/o requiring Facter, however require-ing "puppet" also requires facter and creates several custom facts. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9685) Allow providing required facts during Puppet initialization
Title: Message Title Justin Stoller created an issue Puppet / PUP-9685 Allow providing required facts during Puppet initialization Issue Type: Improvement Assignee: Unassigned Created: 2019/04/25 2:25 PM Priority: Normal Reporter: Justin Stoller During regular usage Puppet looks up values from Facter. In particular to create a node's catalog Puppet asks Facter for fqdn and ip information. The server team would prefer to determine those values at start up and then feed them into Puppet when we initialize it, rather than every JRuby instance having to call Facter's JNI to retrieve them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9640) Fix puppet user management on OS X 10.14
Title: Message Title Jean Bond commented on PUP-9640 Re: Fix puppet user management on OS X 10.14 Thanks Gheorghe Popescu! I've added the information about whitelisting parent process to the existing known issue for macOS 10.14. The user type documentation is generated from code, so the information about limitations on the user type should be added directly to user.rb in the Puppet code repository (puppet/lib/puppet/type). Please add it there if you haven't already done so, and feel free to ping me if you want me to review the PR. Added to known issues: User and group management on 10.14 requires Full Disk Access To manage users and groups with on 10.14, you must grant Full Disk Access (FDA). You must also grant FDA to the parent process that triggers your run. For example: To run in a master-agent infrastructure, you must grant FDA to the pxp-agent. To run from a remote machine with SSH commands, you must grant FDA to sshd. To run commands from the terminal, you must grant FDA to terminal.app. To give access on a machine running 10.14, go to System Preferences > Security & Privacy > Privacy > Full Disk Access, and add the path to the executable, along with any other parent processes you use to run . Alternatively, set up automatic access using Privacy Preferences Control Profiles and a Mobile Device Management Server. PA-2226, PA-2227 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1283) Task wrapper script for running tasks on local transport permissions error
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1283 Task wrapper script for running tasks on local transport permissions error Issue Type: Bug Assignee: Unassigned Created: 2019/04/25 1:50 PM Priority: Normal Reporter: Cas Donoghue Note: This applies only to the local transport. When the task wrapper script which wraps tasks that require data on stdin is written (from an IO object coded in source) it is owned by whatever local user is running bolt. It is currently written to a file called `tempfile` that appears to be written to whatever directory the bolt command is invoked from. When the user specified with run-as tries to copy and chmod that file the task can fail due to permission errors. The following link points to a PR that tried to solve this two ways: https://github.com/puppetlabs/bolt/pull/967#discussion_r278366899 The first was to write the wrapper file directly to the destination with full execute permissions. This handles the case where a root user is running as a less privileged user but fails when a less privileged user is running as root. The second attempt was to try to echo the contents of the wrapper script to the destination as the user specified with run-as. This attempt ran in to limitations around using redirection with run-as that relates to https://tickets.puppetlabs.com/browse/BOLT-1056 Add Comment
Jira (BOLT-1262) File upload can hang with local transport using run-as
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1262 File upload can hang with local transport using run-as Change By: Cas Donoghue Release Notes Summary: Fix issue where `bolt file upload` could hang when using the local transport if the destination file exists. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Jean Bond updated an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Change By: Jean Bond Release Notes Summary: Puppet now uses the ` - - This release fixes an issue where you could no -document` option instead of longer specify multiple logging destinations on the deprecated command line with the `-- no-rdoc --no-ri logdest ` options option. This feature was temporarily broken when installing gems, allowing compatibility with we added the ability to specify a logging destination in ` rubygems puppet.conf ` >= 3 . 0.0. [PUP- 9395 9565 ] documented for 6 (https://tickets . 4 puppetlabs . 2 and 5.5.14, waiting for confirmation on 6.0.9 com/browse/PUP - -jean 9565) 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-1262) File upload can hang with local transport using run-as
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1262 File upload can hang with local transport using run-as Change By: Cas Donoghue 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-1262) File upload can hang with local transport using run-as
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1262 File upload can hang with local transport using run-as Change By: Cas Donoghue Summary: File upload hangs, task wrapper does not respect can hang with local transport using run-as owner 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-1262) File upload can hang with local transport using run-as
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1262 File upload can hang with local transport using run-as Change By: Cas Donoghue In the case where a user specified with run-as tried to upload a file to a destination owned by a user with different privilages privileges a command prompt is raised which causes the command to hang indefinitely. By adding the -f flag to the mv command an appropriate permission error is raised and the operation does not hang. When using the task wrapper, the tempfile is written with the permissions of the user who ran the command and not the run-as user. https://github.com/puppetlabs/bolt/blob/55de205f60b5ca69c1812cec18ef2bec8db47f1b/lib/bolt/transport/local/shell.rb#L70 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...
Jira (BOLT-1280) Update homebrew-puppet (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1280 Update homebrew-puppet (Bolt 1.18.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/25 1:09 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1278) Publish release artifacts (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1278 Publish release artifacts (Bolt 1.18.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/25 1:09 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) Run the Bolt shipping pipeline. Set REF to 1.18.0. If you encounter any issues, ping the on-call person in the #release-new-new Slack channel. Add Comment This message was sent by Atlassian JIRA (v7.7.1#
Jira (BOLT-1279) Update the release spreadsheet (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1279 Update the release spreadsheet (Bolt 1.18.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/25 1:09 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) Update the release google spreadsheet for Bolt 1.18.0. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1282) Send release announcements (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1282 Send release announcements (Bolt 1.18.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/04/25 1:09 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.18.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. 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 1.18.0 is now available".
Jira (BOLT-1281) Docs for bolt release (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1281 Docs for bolt release (Bolt 1.18.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/04/25 1:09 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) Release notes and docs changes for bolt 1.18.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1276) Reconcile git commits, JIRA tickets, and versions (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1276 Reconcile git commits, JIRA tickets, and versions (Bolt 1.18.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/25 1:08 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) 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-1277) Kick off release pipeline (Bolt 1.18.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1277 Kick off release pipeline (Bolt 1.18.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/04/25 1:08 PM Due Date: 2019/04/25 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-04-25) 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-1275) Bolt 1.18.0 2019-04-25 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1275 Bolt 1.18.0 2019-04-25 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/04/25 1:08 PM Priority: Normal Reporter: Cas Donoghue Bolt 1.18.0 2019-04-25 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Lucy Wyman Questions:- How will the user specify where the statefile is? Is this config for the plugin or part of the lookup?- How will the user specify the name of the target?- How will the user specify connection info(host)? Plugin configuration? - Is there anything we can do that is terraform specific? Always unconditionally print At least try shelling out to `tf state` - if it's not available fail. State server on it's own is not supported.Need to have the terraform project directory path, and a warning second optional path to manually verify Puppet code the statefile itself if you have multiple.Should be passed as a comment at top parameter to the lookup, as opposed to a way of configuring the plan lookup Run puppet plan through parser and validator and error if it's invalid (exit nonzero but still print plan) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1195) Generate a PP plan from a simple plan
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1195 Generate a PP plan from a simple plan Change By: Lucy Wyman Once a user has invested in a plan they shouldn't have to start from scratch if they want to add logic that requires writing a full PP plan.`bolt plan convert plan_name`error if already puppetprint puppet code to the console otherwise. Always unconditionally print a warning to manually verify Puppet code as a comment at top of the planRun puppet plan through parser and validator and error if it's invalid (exit nonzero but still print plan) 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
Jira (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Reid Vandewiele commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default UX note: it looks like most configuration options for bolt.yaml use a hyphen "-" character for separating words in multi-word configuration setting names; not underscores "_". Besides being consistent with existing config options, use of a hyphen as a word-separator is aligned with newer command-line flags in Puppet, most regex implementations ideas of what is part of a word vs. characters that can separate words, as well as the general nogui pattern guidance which seems to be "use hyphens as a word separators, NOT underscores, except when there's a technical constraint that dictates otherwise." Admittedly the nogui guidance is focused on things like command-line flags, but I think it applies well to config files as well. Whatever configuration setting we use should use hyphens as word separators, not underscores. If we stick with Nick's original setting name, the setting name would therefore become puppetfile-install-path. Curious though... is this really a "breaking" change, or did we incorrectly implement this? Reading the r10k docs, it sounds like r10k always defaults to "modules", regardless of Puppet's modulepath setting. Is that right? The Puppetfile is documented to support a "moduledir" setting. If we create a bolt.yaml setting for this then, maybe it should just be called puppetfile-moduledir. https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#moduledir 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
Jira (BOLT-1268) Inventory is loaded for actions that do not use it.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1268 Inventory is loaded for actions that do not use it. Change By: Alex Dreyer 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 (BOLT-1269) Prompt for sensitive data from inventory.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1269 Prompt for sensitive data from inventory. Change By: Alex Dreyer 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 (BOLT-1270) eyaml encryption for sensitive inventory data
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1270 eyaml encryption for sensitive inventory data Change By: Alex Dreyer 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 (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Lucy Wyman Questions:- How will the user specify where the statefile is? Is this config for the plugin or part of the lookup?- How will the user specify the name of the target?- How will the user specify connection info(host)?- Is there anything we can do that is terraform specific? Always unconditionally print a warning to manually verify Puppet code as a comment at top of the planRun puppet plan through parser and validator and error if it's invalid (exit nonzero but still print plan) 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. Visi
Jira (BOLT-1274) Stack trace when inventory config is not a hash or nil
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1274 Stack trace when inventory config is not a hash or nil Change By: Lucy Wyman Sprint: Bolt Ready for Grooming 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-1228) "As a new user I want to do ___ and don't know what files I need to have to accomplish that?"
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1228 "As a new user I want to do ___ and don't know what files I need to have to accomplish that?" Change By: Alex Dreyer 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 (BOLT-1228) "As a new user I want to do ___ and don't know what files I need to have to accomplish that?"
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1228 "As a new user I want to do ___ and don't know what files I need to have to accomplish that?" Change By: Lucy Wyman 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 (BOLT-1228) "As a new user I want to do ___ and don't know what files I need to have to accomplish that?"
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1228
"As a new user I want to do ___ and don't know what files I need to have to accomplish that?"
Change By:
Lucy Wyman
This would be a new subcommand to create a skeleton project with the structure described in https://puppet.com/docs/bolt/latest/bolt_project_directories.html#local-project-directory{code}myproject/├── Puppetfile├── README.md (?)├── bolt.yaml├── inventory.yaml└── site-modules└── myproject├── manifests/├── plans/└── tasks/{code}I see 2 use cases here:- I want to create a new project from scratch for developing bolt content- I want to add bolt plans and tasks to my current module / project directoryWe should focus on the first - it seems more common, and will serve newer users where the second seems like a more advanced use case (you already kind of know what you're doing).The subcommand should accept two arguments- The name of the project to create- An optional target directory where to create the project, defaulting to the current directory if not specifiedIf the project already exists in the target directory it should error. We should also make it easy to add the project to the forge, maybe by linking to documentation in the output? Or documenting the process in the bolt docs? Not sure
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1228) "As a new user I want to do ___ and don't know what files I need to have to accomplish that?"
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1228 "As a new user I want to do ___ and don't know what files I need to have to accomplish that?" Change By: Lucy Wyman Summary: Add `bolt project create` command "As a new user I want to create skeleton module do ___ and don't know what files I need to have to accomplish that?" 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-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-1245
Bolt puppetfile install should install to "modules" by default
Change By:
Reid Vandewiele
Currently, the {{bolt puppetfile install}} command will install to the first location on the modulepath:[https://github.com/puppetlabs/bolt/blob/1.16.0/lib/bolt/cli.rb#L416]The install action removes any content not listed in the Puppetfile and reverts any changes made to modules. We should not assume that the entry placed first in the path is the location that a user wants this sort of aggressive cleaning to occur.Historically, {{r10k puppetfile install}} has defaulted to using a directory named {{modules}}:[https://github.com/puppetlabs/r10k/blob/3.1.1/lib/r10k/puppetfile.rb#L48]Also, historically, control repos have been configured to priortizie {{site}} modules by placing them ahead of the {{modules}} directory on the path:[https://github.com/puppetlabs/control-repo/blob/1.0.0/environment.conf#L1]Users following these historical patterns will end up loosing work when {{bolt puppetfile install}} cleans the {{site}} directory._Clarity note: the control-repo template uses {{site-modules}} instead of {{site}} starting with 1.1.0. Many users will have the older {{site}} directory still though, so it is not inappropriate to describe this issue using that name. The issue applies regardless of what directory name is used for control-repo embedded module content. _
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-1245
Bolt puppetfile install should install to "modules" by default
Change By:
Reid Vandewiele
Currently, the {{bolt puppetfile install}} command will install to the first location on the modulepath: [ https://github.com/puppetlabs/bolt/blob/1.16.0/lib/bolt/cli.rb#L416 ] The install action removes any content not listed in the Puppetfile and reverts any changes made to modules. We should not assume that the entry placed first in the path is the location that a user wants this sort of aggressive cleaning to occur.Historically, {{r10k puppetfile install}} has defaulted to using a directory named {{modules}}: [ https://github.com/puppetlabs/r10k/blob/3.1.1/lib/r10k/puppetfile.rb#L48 ] Also, historically, control repos have been configured to priortizie {{site}} modules by placing them ahead of the {{modules}} directory on the path: [ https://github.com/puppetlabs/control-repo/blob/1.0.0/environment.conf#L1 ] Users following these historical patterns will end up loosing work when {{bolt puppetfile install}} cleans the {{site}} directory. _Clarity note: the control-repo template uses {{site-modules}} instead of {{site}} starting with 1.1.0. Many users will have the older {{site}} directory still though, so it is not inappropriate to describe this issue using that name._
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Alex Dreyer commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default I'm ok with adding the option. Officially it will have have to have no default in the 1.x series and get a default of `modules` in 2.0 to avoid making dependencies between config options. 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-1109) Create plugin hook for populating inventory groups dynamically
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1109 Create plugin hook for populating inventory groups dynamically Change By: Alex Dreyer Release Notes Summary: The new experimental version 2 inventory file will now dynamically populate groups from puppetdb queries. 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-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Reid Vandewiele commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default `bolt puppetfile install` is technically an R10K command. There's no reason r10k has to use the same modulepath for provisioning as Bolt does for loading. +1 to the idea Nick Walker gives above. Separate config item. Default it to modules. 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-1109) Create plugin hook for populating inventory groups dynamically
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1109 Create plugin hook for populating inventory groups dynamically Change By: Alex Dreyer Release Notes: Not Needed 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-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Nick Walker commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default Alex Dreyer Can we get a new config option to bolt something like `puppetfile_install_path` ( or I think r10k calls it moduledir) which defaults to the first item in the modulepath but can be overridden? Then in 2.0 we could make the breaking change so that it defaults to modules instead of the first item. I also like Nick Lewis suggestion to check to see if there's something in the directory r10k is going to deploy to and fail if it wasn't previously deployed by r10k and require user interaction. 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-4361) IPv6 aware query operators
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4361 IPv6 aware query operators Issue Type: Improvement Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 10:02 AM Priority: Normal Reporter: Robert Roland It would be great to have query operators in PuppetDB that support IP address ranges (subnets, etc) and these would need to be IPv6 aware. i.e.: hosts in 192.168.1.0/24 or: hosts in 2601:600:967f:cd4a:da42:7bc6::/32 Add Comment This message was sent by Atlassian J
Jira (PDB-4360) pdbbox to support configuring IPv6
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4360 pdbbox to support configuring IPv6 Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 10:00 AM Priority: Normal Reporter: Robert Roland pdbbox needs to support IPv6 (via a flag?), replacing localhost with ip6-localhost, for example and any appropriate listen settings for jetty. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4359) Integration tests that run with IPv4/IPv6 mixed network
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4359 Integration tests that run with IPv4/IPv6 mixed network Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:58 AM Priority: Normal Reporter: Robert Roland We need integration tests designed to work in a mixed IPv4 / IPv6 environment, meaning situations like: Listen for connections on both IPv4 and IPv6 Communicate with PostgreSQL strictly via IPv6 in this environment Add Comment This message wa
Jira (PDB-4358) Integration tests that run with only IPv6
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4358 Integration tests that run with only IPv6 Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:57 AM Priority: Normal Reporter: Robert Roland We need integration tests that run in an IPv6-only environment to ensure compatibility Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4357) Enable the Bouncy Castle FIPS provider
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4357 Enable the Bouncy Castle FIPS provider Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:56 AM Priority: Normal Reporter: Robert Roland See: https://www.bouncycastle.org/fips-java/BCFipsIn100.pdf This requires replacing the Bouncy Castle dependency we currently use with the FIPS compliant one, and some setup. See linked PDF. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sh
Jira (PDB-4356) Migrate db code from md5 to sha1
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4356 Migrate db code from md5 to sha1 Issue Type: Story Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:53 AM Priority: Normal Reporter: Robert Roland There is a function and an aggregate created in psql for PE that uses MD5. These must be replaced with SHA1 variants. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4355) Bring IPv6 support to PuppetDB
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4355 Bring IPv6 support to PuppetDB Issue Type: Epic Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:50 AM Priority: Normal Reporter: Robert Roland 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 unsubscri
Jira (PDB-4354) Work to support FIPS certification on PuppetDB
Title: Message Title Robert Roland created an issue PuppetDB / PDB-4354 Work to support FIPS certification on PuppetDB Issue Type: Epic Assignee: Unassigned Components: PuppetDB Created: 2019/04/25 9:49 AM Priority: Normal Reporter: Robert Roland 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" gro
Jira (BOLT-1245) Bolt puppetfile install should install to "modules" by default
Title: Message Title Adam Buxton commented on BOLT-1245 Re: Bolt puppetfile install should install to "modules" by default The only way I see this could work is to insist that `~/.puppetlabs/modules` is used by default, and check for its existence and then prompt $USER to use it/create it. This could work in conjunction with a new config point that defines whether to use the `user modulepath` or the `bolt modulepath`. I'm using the process with the customer and defaulting the above would work better is Puppet still defaulted to `$USERHOME/.puppetlabs/modules` when run as none root user. (but thats a by the by) 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.
