Jira (PUP-11329) Attempt to redefine entity error on agent if plugins are reloaded
Title: Message Title Corey Osman commented on PUP-11329 Re: Attempt to redefine entity error on agent if plugins are reloaded I ran into this issue. My environment details are below: puppet agent 6.0.5 puppetserver 2019.8.11 stdlib 5.2.0 After changing the stdlib version to 6.6.0 in a new puppet_agent environment I ran into the same error but with the file_line.rb file from stdlib. Note, the default environment for this node is development, so switching environment caused the update to some stdlib functions. It seemed to only affect the file_line function though. puppet agent -t --environment=puppet_agent If I delete the file_line.rb and run puppet agent the problem goes away. However, I would have to do this on many nodes. I ended up reverting back to stdlib 5.2.0 and will upgrade my agents to 6.27.0 where the bug might not be present. Will update this ticket on my findings once I have 6.27,0 and stdlib 6.6.0 back in motion. Error: Could not autoload puppet/type/file_line: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/file_line'. Originally set atfile:///opt/puppetlabs/puppet/cache/lib/puppet/type/file_line.rb?line=1.Error: Failed to apply catalog: Could not autoload puppet/type/file_line: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/file_line'. Originally set atfile:///opt/puppetlabs/puppet/cache/lib/puppet/type/file_line.rb?line=1. Add Comment
Jira (FACT-2953) os codename should use parent os codename
Title: Message Title Corey Osman commented on FACT-2953 Re: os codename should use parent os codename I can contribute this code. Any specific file I should look in? Is this a puppet or facter change. Do I need to reopen the ticket or just reference it? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389690.1614739764000.16071.1650570060030%40Atlassian.JIRA.
Jira (PUP-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman commented on PUP-5652 Re: Windows Package provider does not work with Installshield with MSI files This was so long ago. I have no desire to test this. I would agree with Rob that the docs should be updated with his example unless they already have been. I would just close the ticket. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.86.1452030387000.4726.1636611540031%40Atlassian.JIRA.
Jira (FACT-2953) os codename should use parent os codename
Title: Message Title Corey Osman created an issue Facter / FACT-2953 os codename should use parent os codename Issue Type: Bug Affects Versions: FACT 3.y, FACT 4.y Assignee: Unassigned Created: 2021/03/02 6:49 PM Priority: Normal Reporter: Corey Osman I am using some lesser known distro derivatives of ubuntu and running into issues with how some of the core facts parse os information. Several modules don’t work when puppet installs packages since the distro codename is used instead of the upstream codename. As an example the docker and puppet-agent fail to download packages because those modules rely on the apt module which configures an apt source with a codename that is only useful for the distro maintainer. I think we should be referencing UBUNTU_CODENAME instead if available. # created by the apt module (pisces is distro codename) deb https://pe-std.puppet.vm:8140/packages/2019.8.5/ubuntu-18.04-amd64 pisces puppet6 # https://github.com/puppetlabs/puppetlabs-apt/blob/main/manifests/source.pp#L76
Jira (PUP-10177) yum provider does not allow array of strings
Title: Message Title
Corey Osman updated an issue
Puppet / PUP-10177
yum provider does not allow array of strings
Change By:
Corey Osman
Summary:
{brief summary yum provider does not allow array of issue} strings
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.339935.157660745.2996.1576607580057%40Atlassian.JIRA.
Jira (PUP-10177) {brief summary of issue}
Title: Message Title
Corey Osman created an issue
Puppet / PUP-10177
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 5.y, PUP 6.y
Assignee:
Unassigned
Created:
2019/12/17 10:30 AM
Priority:
Normal
Reporter:
Corey Osman
Puppet Version: Any Puppet Server Version: Any OS Name/Version: RHEL (All versions) When using the puppet_agent module to update an RPM to the latest the install_options flags --enablerepo and --disablerepo only accepts array of hashes and not an array of Strings. This contradictory to the following documentation: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package.rb#L36-L58 PR: Puppet 5.x: https://github.com/puppetlabs/puppet/pull/7879 and Puppet 6.x: {PR to come, will update when available} Desired Behavior: User's should be able to specify any package manager option as an array of String or an array of Hashes. The docs detail the user can pass an array of strings or hashes. However, there are no tests in the puppet code base that back up these claims. Actual Behavior: Only --enablerepo and --disablerepo are special for YUM as they affect which packages are visible to the package manager. The logic that pulls them out for use in things like version checks only looks for Hash form of specifying an option: https://github.com/puppetlabs/puppet/blob/5.5.17/lib/puppet/provider/package/yum.rb#L268-L296 create a /tmp/test.pp file with the following contents:
cat /tmp/test.pp package { 'nginx': ensure => 'latest', install_options => [ '-enablerepo="dev*"' ], } nginx can be any rpm package
Details show that an updated package was available and did not apply, contents of the manifest being applied: root@:~
yum list
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title
Corey Osman commented on PUP-7197
Re: make type aliases from modules available on the agent
"Why validate the data type in the provider, if it's already been validated at compile time?" Correct, it would already be compiled and not required on majority of cases, But if puppet resource was used and someone like me was doing stupid stuff like this in the type code that puppet resource would fail.
Puppet::Pops::Types::TypeParser.singleton.parse("Stdlib::AbsolutePath").instance?(value)
This is an extremely rare case as nobody is doing this and it would only fail on puppet resource. I was just wanting to shoehorn a method to validate input without the awesome resource_api. Take my request with a grain of salt.
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 view this discussion on the web vi
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title
Corey Osman commented on PUP-7197
Re: make type aliases from modules available on the agent
If I want to use the type aliases without the resource API so I can run code like this. Without the datatype on the agent this will not work.
newparam :path do
# includes windows and unix paths
desc 'Absolute path to repository'
isnamevar
validate do |value|
datatype = Puppet::Pops::Types::TypeParser.singleton.parse("Stdlib::AbsolutePath")
raise ArgumentError, "Path must be absolute: #{path}" unless datatype.instance?(value)
end
end
Add Comment
Jira (BOLT-1384) Inventory command
Title: Message Title
Corey Osman commented on BOLT-1384
Re: Inventory command
IMHO, the default usage of this command will be for scripts. If that is the case we should make the default behavior work for the scripts and not against them. So in a case like:
#!/usr/bin/env bash nodes=$(bolt inventory --nodes ubuntu) for node in $nodes; do ssh-copy-id ethos@${nodes} done
I don't want to go hunt down which modifier I need to add in order to not return "55 targets". I also don't want to run the command first only to have it fail on the node called "55" and "targets". So I would like to have this count removed by default.
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312167.1560296026000.52687.1565650860759%40Atlassian.JIR
Jira (BOLT-1384) Inventory command
Title: Message Title Corey Osman commented on BOLT-1384 Re: Inventory command I would need --format=text, --format=json I would prefer to just have the node count removed by default. Use a verbose option if you want the count. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312167.1560296026000.42177.1564777200155%40Atlassian.JIRA.
Jira (BOLT-1384) Inventory command
Title: Message Title Corey Osman commented on BOLT-1384 Re: Inventory command This does satisfy my use case. Just tried this out. However, this creates a new problem in that the node count at the bottom will cause any script written against the output of the inventory command to break. The node count should be removed by default or added as a option. 192.168.70.104 192.168.70.110 192.168.70.119 192.168.70.125 192.168.70.128 192.168.70.135 192.168.70.136 55 targets Add Comment
Jira (BOLT-1384) Inventory command
Title: Message Title
Corey Osman created an issue
Puppet Task Runner / BOLT-1384
Inventory command
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/06/11 4:33 PM
Priority:
Normal
Reporter:
Corey Osman
I would like to have an inventory command to interact with the inventory file, puppetdb or other place bolt retrieves the list of nodes from. This would allow me to see what is in the inventory before running and also write bootstrap scripts outside of bolt This command would prevent me from having to always parse out the inventory file to accomplish the same thing. Example:
#!/usr/bin/env bash
nodes=$(bolt inventory --nodes ubuntu)
for node in $nodes; do
ssh-copy-id ethos@${nodes}
done
Jira (BOLT-1383) Command to copy ssh identity to authorized keys
Title: Message Title Corey Osman created an issue Puppet Task Runner / BOLT-1383 Command to copy ssh identity to authorized keys Issue Type: New Feature Assignee: Unassigned Created: 2019/06/11 4:25 PM Priority: Normal Reporter: Corey Osman The first step when running bolt is to setup an ssh identity in the remote system's authorized_keys file, otherwise the user is burdened with typing passwords. We need a bolt command to perform this step automatically instead of create a bash for loop. This would look something like: bolt ssh-copy-id --nodes ubuntu Bolt would gather the nodes and use the default ssh identity or the one provided in the inventory file and use ssh-copy-id utility to copy over the identity and place in authorized keys file on the remote system. Add Comment
Jira (FACT-1918) Facter is pinned to ruby version 2.1.7
Title: Message Title Corey Osman created an issue Facter / FACT-1918 Facter is pinned to ruby version 2.1.7 Issue Type: Bug Assignee: Unassigned Created: 2019/05/02 5:16 PM Priority: Normal Reporter: Corey Osman The facter gemspec is pinned to ruby 2.1.7 which is causing gem installation errors. https://github.com/puppetlabs/facter/blob/master/lib/gemspec.in#L19 facter-3.11.8 requires ruby version ~> 2.1.7, which is incompatible with the current version, ruby 2.4.5p335 Steps to reproduce: Install the puppet-agent (any version will work) Install pdk the gem (/opt/puppetlabs/puppet/bin/gem install pdk) Create a new module using the pdk (pdk new module test) cd test && pdk unit test The failure should occur as it tries to load the facter gem using the specification. Workaround Remove the patch version from the 2.1.7 in the gemspec for post install issues Gem::Specification.new do |s|
Jira (BOLT-305) Task metadata should allow defaults for parameter values
Title: Message Title
Corey Osman commented on BOLT-305
Re: Task metadata should allow defaults for parameter values
I also want this feature. What I would like to see is something like defaultValue defined in the task metadata:
"parameters": {
"channel": {
"description": "The repo distribution channel",
"type": "Enum[testing, unstable, stable]",
"defaultValue": "stable"
}
}
Currently I can accomplish the same thing using the script language. But to have a language agnostic method might be useful. channel=${PT_channel:-stable} - Bash channel= ENV['PT_channel'] || 'stable' - ruby Of course this also means that when I run the show task command I should also see the configured defaults as well.
Add Comment
Jira (PUP-7430) Removal of Rgen methods breaks third party tools
Title: Message Title Corey Osman updated an issue Puppet / PUP-7430 Removal of Rgen methods breaks third party tools Change By: Corey Osman I am the author of puppet-retrospec (https://github.com/nwops/puppet-retrospec) which is a fairly popular tool for automating module content including rspec-puppet tests.Puppet 5 removes the Rgen related code and puppet-retrospec relies heavily on these methods to find patterns in code. In Puppet 4 the eContainer method allowed retrospec to perform a deep inspection of code by looking forward and backward to calculate puppet coding patterns. This was a huge benefit over the old Puppet 3 AST model.Without the eContainer method the puppet-retrospec gem will not work in the current form. This would cause me to rewrite a major portion of the retrospec gem which I will probably not do as I have too many other things to do, and I just rewrote it to use puppet 4 parser last year. My current work around is to just vendor the 4.x gem like I am currently doing, but eventually this will need to change if there are significant feature changes / additions in puppet 5. I understand this is a tricky situation, you need to remove what was seen as unused code (Rgen) in order to move the platform forward which is totally fine, but I would like to see some sort of replacement for what was removed. I don't think 3rd party tools should have to implement their own lexer / parser tooling for the puppet language when the puppet library comes with an awesome one already. Third party tools should be able to utilize the lexer / parser API built into puppet without fear of breaking changes.For example the puppet-lint tool uses it's own lexer which is good because puppet 5 will not break it. However, the puppet-lint lexer also suffers from lack of puppet 4 support and any future additions to the puppet language will require more work. So really it is a huge burden for the tool maker to keep their own lexer current. Especially, when puppet ships with one.What I would like to see:1, A separate gem for 3rd party tooling, with Rgen, supported integration API, docs and examples2. Put rgen back into puppet 53. Rewrite the broken code in retrospec-puppet and other gems ;) Add Comment
Jira (PUP-7430) Removal of Rgen methods breaks third party tools
Title: Message Title Corey Osman created an issue Puppet / PUP-7430 Removal of Rgen methods breaks third party tools Issue Type: Bug Affects Versions: PUP 5.0.0 Assignee: Unassigned Created: 2017/04/05 8:23 PM Priority: Normal Reporter: Corey Osman I am the author of puppet-retrospec (https://github.com/nwops/puppet-retrospec) which is a fairly popular tool for automating module content including rspec-puppet tests. Puppet 5 removes the Rgen related code and puppet-retrospec relies heavily on these methods to find patterns in code. In Puppet 4 the eContainer method allowed retrospec to perform a deep inspection of code by looking forward and backward to calculate puppet coding patterns. This was a huge benefit over the old Puppet 3 AST model. Without the eContainer method the puppet-retrospec gem will not work in the current form. This would cause me to rewrite a major portion of the retrospec gem which I will probably not do as I too many other things to do, and I just rewrote it to use puppet 4 parser last year. My current work around is to just vendor the 4.x gem like I am currently doing, but eventually this will need to change if there are significant feature changes / additions in puppet 5. I understand this is a tricky situation, you need to remove what was seen as unused code (Rgen) in order to move the platform forward which is totally fine, but I would like to see some sort of replacement for what was removed.
Jira (PUP-7364) Parser result no longer contains current method
Title: Message Title Corey Osman created an issue Puppet / PUP-7364 Parser result no longer contains current method Issue Type: Bug Affects Versions: PUP 5.0.0 Assignee: Unassigned Created: 2017/03/16 9:59 AM Priority: Normal Reporter: Corey Osman The puppet debugger uses the AST model to get a model object in order to import itself into the known resource types. In order to make this work with puppet 5 I had to refactor my code slightly to account for the missing method. Not a huge deal but this might break other third party code. Previously I was calling parse_result.current to get the model. However, with puppet 5 I actually don't need to do that anymore since the model object is the parsed result. But because puppet-debugger supports puppet 3-5 I had to write the following code to work around the issue. Puppet 5 should add a current method to the parsed_result object that points to itself, thus keeping third party integrations working. Example: # adds backward compatible call so we don't break third party programs.
Jira (PUP-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman commented on PUP-5652 Re: Windows Package provider does not work with Installshield with MSI files Rob Reynolds It is not about having internal sources. It is about having to recreate all the choco packages that have hard coded external dependencies. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' command
Title: Message Title Corey Osman commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' command This is occuring on my setup as well. Using PE 2016.04.02 . It is super easy to reproduce. config = `puppet config print config` cat > $config << 'EOF' [main] environment = dev EOF puppet config print environment Add Comment
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman commented on PUP-4800 Re: Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly A regex example is also here: http://rubular.com/r/wCSGrtZmhI Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title
Corey Osman updated an issue
Puppet / PUP-4800
Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Change By:
Corey Osman
I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content.# regex that has trouble with my ini contenthttps://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file.My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. {code:ruby} inffile = 'c:\\windows\\temp\\secedit.inf' secedit(['/export', '/cfg', inffile, '/quiet'])inf = Puppet::Util::IniConfig::PhysicalFile.new(inffile).read {code} So the regex can't handle the awesomeness of windows files and I assume this affects all versions of puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-bu
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman updated an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Change By: Corey Osman I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content.# regex that has trouble with my ini contenthttps://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file.My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. inffile = 'c:\\windows\\temp\\secedit.inf' secedit(['/export', '/cfg', inffile, '/quiet'])inf = Puppet::Util::IniConfig::PhysicalFile.new(inffile).readSo the regex can't handle the awesomeness of windows files and I assume this affects all versions of puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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...@googlegr
Jira (PUP-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman commented on PUP-5652 Re: Windows Package provider does not work with Installshield with MSI files Do I still need to provide an example? I am upgrading to PE 2016 and will check if the problem still exists. Rob Reynolds I wish I could use chocolatey but at the time there was no enterprise edition as our systems don't have internet. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2410) Create method to switch skeletons when creating new modules
Title: Message Title Corey Osman commented on PUP-2410 Re: Create method to switch skeletons when creating new modules This ticket has fallen into a black hole. I created puppet-retrospec to fill my needs so closing this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-5652) Windows Package provider does not work with Installshield with MSI files
Title: Message Title Corey Osman created an issue Puppet / PUP-5652 Windows Package provider does not work with Installshield with MSI files Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Aaron Armstrong Components: PE, Types and Providers Created: 2016/01/05 1:46 PM Environment: PE 3.8 Priority: Normal Reporter: Corey Osman Reference Material: http://unattended.sourceforge.net/installers.php (InstallShield with MSI) The windows package provider incorrectly quotes or adds a space when combining the install options. Because the Installshield installer is a wrapper exe for another installer, options must be specially quoted and passed in as an argument. However, puppet can't seem to get the quotes right no matter what I do. Example:
Jira (PUP-3745) Group membership should be a type of its own.
Title: Message Title Corey Osman commented on PUP-3745 Re: Group membership should be a type of its own. Is this module usable yet? I would agree with Nigel. I want to define users, and then I want to define their groups based on which software is deployed. I usually don't know those two pieces up front which is why I can't do everything at once. Additionally, since we are using centrify many times the user doesn't even exist yet until the first login. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1526) Package type should support environment variables
Title: Message Title Corey Osman commented on PUP-1526 Re: Package type should support environment variables Add me to the list as well. I was trying to undo the mess symantec has done with their packaging system and it appears that it requires a response file in order to install the package which can only be supplied via a environment variable, despite that it just copies the response file to /etc dir! I know I can always use an exec but it would be nice to throw and environment variable to override some of the behavior and use the native package type. I know rpms are not supposed to be like this but they managed to make a single installer for all unix systems with configuration built in. # get RESPONSE settings (from request script) if [ "$RESPONSE_FILE" = "" ]; then # Try to guess location (i.e. on Solaris SIS_TMPDIR is already in the env) [ "$SIS_TMPDIR" ] && RESPONSE_FILE=$SIS_TMPDIR/SYMCcsp.response || \ RESPONSE_FILE=SYMCcsp.response fi Add Comment
Jira (PUP-4888) Create Powershell Provider command helper
Title: Message Title
Corey Osman updated an issue
Puppet / PUP-4888
Create Powershell Provider command helper
Change By:
Corey Osman
Currently when we create custom providers and want to "shell out" to run a system command there is a helper command that finds the absolute path to the command and creates a method call for the provider.{code:ruby}commands :secedit => 'secedit'def self. instances instances = secedit(['/export', '/cfg', inffile, '/quiet'])end{code}This works great for any command even on windows. However, powershell can often provide a better interface to the system than a one off system command can provide especially when using external modules.When using external modules in powershell it is often necessary to install a feature or download the powershell module from a url. So if the system does not have the module than the powershell command should never run. Note: this request is not about installing modules. To make custom providers for windows easier we need a helper method similar to the commands method that finds powershell and all the modules we need imported.An example of this on the command line1. powershell2. import-module grouppolicy3. Get-GPOThe helper code I would like to see should find suitability by checking for installed modules and optionally powershell version.{code:ruby}Puppet::Type.type(:local_security_policy).provide(:policy) do powershell :version => 2, :imported_modules => ['grouppolicy', 'other module'], :name => :gpo def self.instances gpo(['Get-GPO']).split("\n").each {|p| new(p) } endend{code}Now my wish is that this powershell helper will create a instance method called gpo and load all the powershell modules I defined and ensure its using powershell version 2. If any of these requirements are not met than the provider will fail suitability. I think this is important because these modules represent additional requirements that must be met that we can't assume are on the system. Additionally, It will also be good to allow the user to pass in the command to run in powershell as well. {code:ruby} powershell :version => 2, :imported_modules => ['grouppolicy', 'other module'], :name => :gpo-list, :command => 'gpo-list'gpo-list(['--all']){code}
Add Comment
Jira (PUP-4888) Create Powershell Provider command helper
Title: Message Title
Corey Osman updated an issue
Puppet / PUP-4888
Create Powershell Provider command helper
Change By:
Corey Osman
Currently when we create custom providers and want to "shell out" to run a system command there is a helper command that finds the absolute path to the command and creates a method call for the provider. {code:ruby} commands :secedit => 'secedit'def self. instances instances = secedit(['/export', '/cfg', inffile, '/quiet'])end {code} This works great for any command even on windows. However, powershell can often provide a better interface to the system than a one off system command can provide especially when using external modules.When using external modules in powershell it is often necessary to install a feature or download the powershell module from a url. So if the system does not have the module than the powershell command should never run. Note: this request is not about installing modules. To make custom providers for windows easier we need a helper method similar to the commands method that finds powershell and all the modules we need imported.An example of this on the command line1. powershell2. import-module grouppolicy3. Get-GPOThe helper code I would like to see should find suitability by checking for installed modules and optionally powershell version. {code:ruby} Puppet::Type.type(:local_security_policy).provide(:policy) do powershell :version => 2, :imported_modules => ['grouppolicy', 'other module'], :name => :gpo def self.instances gpo(['Get-GPO']).split("\n").each {|p| new(p) } endend {code} Now my wish is that this powershell helper will create a instance method called gpo and load all the powershell modules I defined and ensure its using powershell version 2. If any of these requirements are not met than the provider will fail suitability. I think this is important because these modules represent additional requirements that must be met that we can't assume are on the system.
Add Comment
This message was sent by
Jira (PUP-4888) Create Powershell Provider command helper
Title: Message Title Corey Osman created an issue Puppet / PUP-4888 Create Powershell Provider command helper Issue Type: New Feature Assignee: Unassigned Created: 2015/07/16 10:49 AM Environment: Windows environment Priority: Normal Reporter: Corey Osman Currently when we create custom providers and want to "shell out" to run a system command there is a helper command that finds the absolute path to the command and creates a method call for the provider. commands :secedit => 'secedit' def self. instances instances = secedit(['/export', '/cfg', inffile, '/quiet']) end This works great for any command even on windows. However, powershell can often provide a better interface to the system than a one off system command can provide especially when using external modules. When using external modules in powershell it is often necessary to install a feature or download the powershell module from a url. So if the system does not have the module than the powershell command should never run. Note: this request is not about installing modules. To make custom providers for windows easier we need a helper method similar to the commands method that finds powershell and all the modules we need imported. An example of this on the command line 1. powershell 2. import-module grouppolicy 3. Get-GPO The helper code I would like to see should find suitability by checking for installed modules and optionally powershell
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman created an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Issue Type: Bug Assignee: Unassigned Created: 2015/06/30 10:12 AM Labels: windows Priority: Normal Reporter: Corey Osman I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content. regex that has trouble with my ini content https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151 The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34 At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file. My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. inffile = 'c:\\windows\\tempsecedit.inf' secedit(['/export', '/cfg', inffile, '/quiet']) inf = Puppet::Util::IniConfig::Physi
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I think what really needs to happen here is that there should be an official document on how to setup a windows based puppet development environment that details everything required. As I mentioned above there is no official document and I had to piece together how to do this by opening a ticket. So I would like to have have another ticket created that focuses on this much needed document. This is important because sometimes many native types/provider/custom facts fail the puppet run when run on windows which is something we can't easily test for until there is an official way to setup a puppet windows dev environment and optionally run on CI systems. My original problem was not fixed however in that we can still not test against PE on windows due to a rake issue. But if PE is not a requirement for having a puppet dev machine I honestly don't mind switching to puppet open source but there just needs to an official document that says what to do. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests There is a bug with the puppet labs spec helper where it doesn't create symlinks on windows which is why it can't find the site-test class. This was fixed in a later version but you are currently using 0.8.2. See version 0.9.0 https://github.com/puppetlabs/puppetlabs_spec_helper/blob/master/CHANGELOG Also the latest version of puppet labs_spec_helper 0.9.0 also introduced a big issue with respec3 where you are now forced to use rspec2. It should work fine with respec2 but just warning you about the issue with rspec3. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I created a sample gist to auto setup a puppet dev environment on windows. It could require a few more tweaks but it was created to suit my needs. This is useful for bootstrapping an environment. https://gist.github.com/logicminds/fa774e01862ef3ae1156 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3857) version of gem bundled with puppet 3.7.3-x64 on windows has bad SSL certs
Title: Message Title
Corey Osman commented on PUP-3857
Re: version of gem bundled with puppet 3.7.3-x64 on windows has bad SSL certs
Additionally, for powershell users this could be used as well.
powershell -Command "(New-Object System.Net.WebClient).DownloadFile('https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/AddTrustExternalCARoot-2048.pem', 'C:\Program Files\Puppet Labs\Puppet Enterprise\sys\ruby\lib\ruby\2.0.0\rubygems\ssl_certs\AddTrustExternalCARoot-2048.pem')"
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3857) version of gem bundled with puppet 3.7.3-x64 on windows has bad SSL certs
Title: Message Title Corey Osman commented on PUP-3857 Re: version of gem bundled with puppet 3.7.3-x64 on windows has bad SSL certs There was a ruby gems ssl issue. The entire world was affected. You can do this as a work around: curl https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/AddTrustExternalCARoot-2048.pem -O 'C:\Program Files\Puppet Labs\Puppet Enterprise\sys\ruby\lib\ruby\2.0.0\rubygems\ssl_certs\AddTrustExternalCARoot-2048.pem' Assuming your using PE. Otherwise you will need modify the path to your ruby. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests This is how I updated the cert curl https://raw.githubusercontent.com/rubygems/rubygems/master/lib/rubygems/ssl_certs/AddTrustExternalCARoot-2048.pem -O 'C:\Program Files\Puppet Labs\Puppet Enterprise\sys\ruby\lib\ruby\2.0.0\rubygems\ssl_certs\AddTrustExternalCARoot-2048.pem' Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests This is really helpful, thanks for providing your "setup script". We were using cygwin to install ruby but this is obviously the better way. Completely forgot about choco. Is this setup already documented? If not, I might write some documentation to get this setup. Perhaps is there a module to install all these packages already? If not I will create one. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Its hard enough to have windows folks use the command line. To tell them they need to install cygwin, ruby (compile it) and and also install the giant list of other runtime dependencies that either come with puppet or with the module (bundle install) is just too much. My locally documented approach was to do the following. 1 install PE 2. Install git for windows (additionally, choose option to add unix tools to cmd path) 3. Development within the puppet command prompt. 4. Use Geppetto to edit files. This takes 5 minutes to setup and its completely straight forward. Install additional gems into PE's environment does not pose any risk because its a development environment and can be disposed of at any time. The only thing I dislike about this setup is that its based of the windows command prompt and not the cygwin bash prompt. For anybody reading this, the work around is to either use a non-PE environment suggested above or use bundle exec rspec spec. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title
Corey Osman commented on PUP-3782
Re: modules on windows cannot run rake tasks to run unit tests
This is the error one should get.
C:\Program Files\Puppet Labs\lmc-test>bundle exec rake spec "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Pro gram Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec -core-3.1.7/lib';'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ru by/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/exe/rspec --patter n 'spec/ {classes,defines,unit,functions,hosts,integration}/*/_spec.rb' --color C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe: No such fi le or directory – C:/Program (LoadError) "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Pro gram Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec -core-3.1.7/lib';'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ru by/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/exe/rspec --patter n 'spec/{classes,defines,unit,functions,hosts,integration}
/*/_spec.rb' --color failed
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Yea, it works when ruby does not have spaces in the path. However puppet enterprise installs with spaces so its not something I can fix by removing the spaces. So a few issues here: 1. Change PE to install in path that does not contain spaces 2. Fix upstream rake command to find ruby better 3. Attach bandaid fix in puppetlabs_spec_helper to accommodate this issue on windows Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests I believe the problem lies with the following: 1. rake spec command doesn't wrapped ruby rspec in quotes 2. Since ruby is installed c/program\ files/puppet\ labs the command fails If ruby were installed under c/puppet_labs/ this problem would not exist. The work around here is to run bundle exec rspec spec. However, this is a different workflow that is not documented in puppet labs spec helper and is only needed on the windows platform to get around the misquoting issue. The issue might be how rake is calling ruby to execute rspec on windows. Should there be one-off rake tasks for windows? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests You can also reproduce like this 1. install pe 3.7 x64 on windows 2. open puppet command prompt 3. puppet module generate test-module1 4. cd test-module1 5. bundle install 6. bundle exec rake spec Its not module specific unless someone specifically works around this issue in their own rakefile. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman commented on PUP-3782 Re: modules on windows cannot run rake tasks to run unit tests Which modules did you test? Did you test them on windows and run the unit test on a windows system? I would say all the modules but most windows modules don't even has tests or they suffer from dependencies issues. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman assigned an issue to Hunter Haugen Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Corey Osman Assignee: Corey Osman Hunter Haugen Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman assigned an issue to Corey Osman Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Change By: Corey Osman Assignee: Hunter Haugen Corey Osman Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3782) modules on windows cannot run rake tasks to run unit tests
Title: Message Title Corey Osman created an issue Puppet / PUP-3782 modules on windows cannot run rake tasks to run unit tests Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Hunter Haugen Components: Windows Created: 2014/12/18 2:04 PM Priority: Normal Reporter: Corey Osman When trying to run module unit tests on windows there seems to be an issue around shell escaping during the run of rspec. See output at bottom. Basically since windows has spaces in paths the rake command does not escape spaces. I believe this to be an issue in puppetlabs_spec_helper. Steps to reproduce: 1. install pe 3.7 x64 on windows 2. open puppet command prompt 3. gem install bundler 4. Install git and include option to have git in the windows command prompt so git is accessible in the puppet command prompt 5. git clone https://github.com/logicminds/site_test.git 6. bundle install 7. bundle exec rake spec 8. Watch the house burn down. "C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/bin/ruby.exe" -I'C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-core-3.1.7/lib';'C:/Program Files/Puppe t Labs/Puppet Enterprise/sys/ruby/lib/ruby/gems/2.0.0/gems/rspec-support-3.1.2/lib' C:/Program Files/Puppet Labs/Puppet Enterprise/sys/ruby/
Jira (PUP-2410) Create method to switch skeletons when creating new modules
Title: Message Title Corey Osman created an issue Puppet / PUP-2410 Create method to switch skeletons when creating new modules Issue Type: New Feature Assignee: Unassigned Created: 30/Apr/14 11:11 PM Labels: module generate skeleton Priority: Normal Reporter: Corey Osman Having generalized some puppet code down to a generic level where providing data is the only requirement to making puppet code. And very similar to std mod https://github.com/stdmod/puppet-skeletons. I want a way how to tell puppet generate to use a different skeleton without swapping skeleton code out. We need a way to specify types of skeletons. Example: ```bash puppet module generate --type standard lmc-mynewmod puppet module generate --type simple lmc-myothernewmod ``` With this functionality I can produce skeleton code to easily create modules that I have generalized and I can just use puppet generate --type javaapp to create a more specific module based on the skeleton. Add Comment
