Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title Daniele Sluijters commented on PUP-2551 Re: Certname must be lowercase error not helpful I'm saying that an error message as silly as that would already be an improvement over the current 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 (PDB-1200) Investigate f20 acceptance test failures
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1200 Investigate f20 acceptance test failures Change By: Rob Browning For example: https://jenkins.puppetlabs.com/job/platform_puppetdb_int-sys-legacystable/335/ (Marked that build as "keep forever" for now.) 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position And you are right, the feature allowing required parameters after optional is only available from Ruby 1.9.x and we need this for 3x where we must support Ruby 1.8.7. Using a Proc / yield is better in any case. 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position Did you verify the performance numbers? Is the difference as big on later rubies? Since you found that it is possible to give the block with &Proc.new it should be possible to create a derived Proc class that can be directly called. Say like this: class PuppetProc < Proc def initialize(closure) @closure = closure end def call(*args) @closure.call(*args) end end I experimented with that, but stumbled on a small problem since Proc requires a block to be given to new - I guess new can be overridden as well to do the initialization - the above sample requires that the PuppetProc is created like this:
Jira (PDB-1144) Is there a bug targeted at the release for every commit?
Title: Message Title Rob Browning commented on PDB-1144 Re: Is there a bug targeted at the release for every commit? As opposed to the description of this ticket, followed the corresponding 3.b. here: https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process i.e. "look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release". 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Thomas Hallgren commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position Regarding default values in dispatch. It does have one disadvantage. A ruby parameter default value is an arbitrary _expression_ that is evaluated when the invocation is made. Placing them in the dispatch means that the evaluation happens when the function is loaded. Perhaps it doesn't matter much since defaults usually have static data nature but I thought it worth mentioning. 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Thomas Hallgren commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position The above syntax gives an error in Ruby 1.8.x (and travis builds still use that for 3.7.x it seems). I've done some tests that pass a real ruby block instead. The resulting code is clean and simple. I stretched it one step further since I found out that passing a &block is much more expensive than using yield. Going back to your approach where the block simply returns the puppet_lambda without executing it makes for a really nice API where we have two options of passing the block. A ruby yield block can be passed as &Proc.new (see above link) or, we can simply yield, get the ruby lambda and then pass that as a normal parameter. Some samples showing how our current functions would change (dispatch declarations unchanged): with function: before def with(*args) args[-1].call(*args[0..-2]) end after def with(*args) yield.call(*args) end scanf function: before
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title Henrik Lindberg commented on PUP-2551 Re: Certname must be lowercase error not helpful Daniele Sluijters not sure I understand what you are saying - is that an error message that you get, or are you saying that an error message like that would be bad if it was expressed that way? (it is not a good error message in any case). Asking because I could not find a message that looks like that on master (tried a couple of variants). 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position I looked into what can be done with ruby, and it is possible to have required parameters after optional. Thus if the method dispatched to has optional parameters followed by a required block, the method would be written: def foo(a, b=1, c=2, block) end Then, if called with 2 parameters, this will give values to a, and block. The parameters b and c will get default values. If called with three parameters, a will get the first value, b the second, and block the third. etc. The tricky signature is optional arguments followed by an optional block. We could solve this by always giving a nil for the block if not present. The method being dispatched to can then use a non optional last block argument that will be nil. It will not trigger its default value, but that value would typically be nil anyway. I do like the ability to define default values in the dispatch - you could in theory dispatch to the same method from multiple dispatchers and you may want to use different default values. As that is probably a bigger change, I can settle for just passing optional block as nil when not given. This is far better than the idea with using a Ruby proc (or a class derived from Proc) since it makes it difficult to pass the block on to another function. Add Comment
Jira (PUP-3978) Missing values for optional parameters places block at wrong position
Title: Message Title
Thomas Hallgren commented on PUP-3978
Re: Missing values for optional parameters places block at wrong position
I like your proposal. Perhaps it could be improved further?
The dispatcher calls the method like this:
f.send(:dispatched_to, *args) { |*block_args| the_block.call(*block_args) }
The method that is being dispatched to can do this:
def dispatched_to(*args, &block)
# call the puppet_lambda with arguments
block.call('foo', 'fee')
...
end
Add Comment
Jira (PUP-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Thomas Hallgren commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position I found another ambiguity when investigating this issue. The arg_count(min, max) will allow max to be the symbol :default. What is the difference between that and using last_captures_rest ? Doesn't one imply the other? 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title Henrik Lindberg commented on PUP-3978 Re: Missing values for optional parameters places block at wrong position How is this ticket different from PUP-3977 ? Looks like a duplicate. 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title
Henrik Lindberg commented on PUP-3978
Re: Missing values for optional parameters places block at wrong position
We could also pass the puppet block as a ruby block. Making that block be the actual puppet block with correct parameters etc requires se gymnastics, and will lose information about parameter types. We could instead just deliver the puppet block when yielding to the ruby block.
The dispatcher calls the method like this:
f.send(:dispatched_to, *args) { the_block }
The method that is being dispatched to can do this:
def dispatched_to(*args, &block)
puppet_lambda = block.call
...
end
or some variation of that (not declaring the block and checkinw with block_defined, and using yield) etc.
Add Comment
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Kylo Ginsberg commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode I don't know much about the useful scenarios - would we want this to be optional even if RDP is enabled/installed? That might guide whether there's an additional parameter needed for the package type or if this just Does the Right Thing without being told to. 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-3979 Windows Package Should Switch between Execute and Install Mode Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-3979
Windows Package Should Switch between Execute and Install Mode
Change By:
Rob Reynolds
Given a user is RDPing into a box and causing a Puppet Agent run or running {{puppet apply}} system has Remote Desktop Services installed , the Windows Package provider should switch between install and execute mode, so that proper RDP practices are followed. From [ServerFault|http://serverfault.com/questions/665896/install-applications-on-windows-rdp-servers-with-puppet]: {quote}The scenario is installing Windows applications with Puppet on a Windows RDP server. I have Puppet install the applications without problem, but per the best practice, you're supposed to be in install mode when doing so, and switching back to execute mode.I can do the following and it works:{noformat}package {'Adobe AIR': ensure => '15.0.0.356', source => '\\myserver\adobeair.exe', install_options => ['-silent', '-eulaAccepted'], require => Exec['installmode'], before => Exec['executemode'],}exec {'installmode': command => 'c:/Windows/System32/change.exe user /install',}exec {'executemode': command => 'c:/Windows/System32/change.exe user /execute',}{noformat}What I'm trying to solve here is that everytime Puppet runs, it considers that something was done as the two Exec run each time regardless if the application really install or not.I would like to silence the execution of Exec, or find a better way to switch between install and execute mode.{quote}h4. References* https://technet.microsoft.com/en-us/library/cc742815.aspx* https://support.microsoft.com/kb/320185?wa=wsignin1.0* http://www.howtogeek.com/100836/how-to-correctly-install-applications-on-a-remote-desktop-server/* http://ss64.com/nt/change.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-3979
Windows Package Should Switch between Execute and Install Mode
Change By:
Rob Reynolds
Given a system has Remote Desktop Services installed, the Windows Package provider should switch between install and execute mode, so that proper RDP practices are followed. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiuser environment are created during the installation process. From [ServerFault|http://serverfault.com/questions/665896/install-applications-on-windows-rdp-servers-with-puppet]: {quote}The scenario is installing Windows applications with Puppet on a Windows RDP server. I have Puppet install the applications without problem, but per the best practice, you're supposed to be in install mode when doing so, and switching back to execute mode.I can do the following and it works:{noformat}package {'Adobe AIR': ensure => '15.0.0.356', source => '\\myserver\adobeair.exe', install_options => ['-silent', '-eulaAccepted'], require => Exec['installmode'], before => Exec['executemode'],}exec {'installmode': command => 'c:/Windows/System32/change.exe user /install',}exec {'executemode': command => 'c:/Windows/System32/change.exe user /execute',}{noformat}What I'm trying to solve here is that everytime Puppet runs, it considers that something was done as the two Exec run each time regardless if the application really install or not.I would like to silence the execution of Exec, or find a better way to switch between install and execute mode.{quote}h4. References* https://technet.microsoft.com/en-us/library/cc742815.aspx* https://support.microsoft.com/kb/320185?wa=wsignin1.0* http://www.howtogeek.com/100836/how-to-correctly-install-applications-on-a-remote-desktop-server/* http://ss64.com/nt/change.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-3979
Windows Package Should Switch between Execute and Install Mode
Change By:
Rob Reynolds
Given a user is RDPing into a box and causing a Puppet Agent run or running {{puppet apply}}, the Windows Package provider should switch between install and execute mode, so that proper RDP practices are followed.From [ServerFault|http://serverfault.com/questions/665896/install-applications-on-windows-rdp-servers-with-puppet]: {quote}The scenario is installing Windows applications with Puppet on a Windows RDP server. I have Puppet install the applications without problem, but per the best practice, you're supposed to be in install mode when doing so, and switching back to execute mode.I can do the following and it works:{noformat}package {'Adobe AIR': ensure => '15.0.0.356', source => '\\myserver\adobeair.exe', install_options => ['-silent', '-eulaAccepted'], require => Exec['installmode'], before => Exec['executemode'],}exec {'installmode': command => 'c:/Windows/System32/change.exe user /install',}exec {'executemode': command => 'c:/Windows/System32/change.exe user /execute',}{noformat}What I'm trying to solve here is that everytime Puppet runs, it considers that something was done as the two Exec run each time regardless if the application really install or not.I would like to silence the execution of Exec, or find a better way to switch between install and execute mode.{quote}h4. References* https:// technet.microsoft.com/en-us/library/cc742815.aspx* https:// support.microsoft.com/kb/320185?wa=wsignin1.0* http://www.howtogeek.com/100836/how-to-correctly-install-applications-on-a-remote-desktop-server/* http://ss64.com/nt/change.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Rob Reynolds commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Sweet, thank you for the clarification. That's what I was looking for. 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-3978) Missing values for optional parameters places block at wrong position
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-3978
Missing values for optional parameters places block at wrong position
Change By:
Thomas Hallgren
A puppet function created using optional parameters followed by a block, that then gets called without providing a value for those optional parameters, will cause the weaving logic to create an arguments array that is too short, leaving the block that is supposed to be last, at the wrong position (it's simply passed on at the position it's placed in by the caller).The fact that a block isn't really a block but a normal parameter in Ruby makes the optional parameter paradigm inconsistent in the dispatch declaration. It can only work without the block since in order to put the block last, a value must be present for each parameter in the invocation. This in turn means that using normal ruby syntax to set parameter default values will fail (passing {{ nil }} overrides such a default setting).On solution would be to provide a parameter default value in the dispatch configuration as an optional fourth third argument to _param_ and require that the ruby method that the dispatch is targeting never has any optional parameters (the method arity _arity_ must never be negative). The default value would be optional in itself and default to {{ nil }} . When given, it must of course comply with the parameter type _type_ (which is another reason to put it there instead of in the ruby method declaration, defaults declare there doesn't have this requirement).
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Etienne Lacombe commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Just a correction, this is not only when the administrator is running Puppet from an RDP session. According to MS documentation, that is the way to install applications on an RDP server - regardless of whether you are, as admin, accessing the server through RDP or local console. https://technet.microsoft.com/en-us/library/cc742815.aspx To ensure that an application is installed correctly to work in a multiuser environment, you must put the RD Session Host server into a special installation mode before you install the application on the RD Session Host server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiuser environment are created during the installation process. This applies only to a server with the RDP feature installed. 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title
Rob Reynolds updated an issue
Puppet / PUP-3979
Windows Package Should Switch between Execute and Install Mode
Change By:
Rob Reynolds
Given a user is RDPing into a box and causing a Puppet Agent run or running {{puppet apply}}, the Windows Package provider should switch between install and execute mode, so that proper RDP practices are followed. From [ServerFault|http://serverfault.com/questions/665896/install-applications-on-windows-rdp-servers-with-puppet]: {quote}The scenario is installing Windows applications with Puppet on a Windows RDP server. I have Puppet install the applications without problem, but per the best practice, you're supposed to be in install mode when doing so, and switching back to execute mode.I can do the following and it works:{noformat}package {'Adobe AIR': ensure => '15.0.0.356', source => '\\myserver\adobeair.exe', install_options => ['-silent', '-eulaAccepted'], require => Exec['installmode'], before => Exec['executemode'],}exec {'installmode': command => 'c:/Windows/System32/change.exe user /install',}exec {'executemode': command => 'c:/Windows/System32/change.exe user /execute',}{noformat}What I'm trying to solve here is that everytime Puppet runs, it considers that something was done as the two Exec run each time regardless if the application really install or not.I would like to silence the execution of Exec, or find a better way to switch between install and execute mode.{quote}h4. References* https://support.microsoft.com/kb/320185?wa=wsignin1.0* http://www.howtogeek.com/100836/how-to-correctly-install-applications-on-a-remote-desktop-server/* http://ss64.com/nt/change.html
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Rob Reynolds commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Josh Cooper Ethan Brown - I am leaving this in Open status pending more discussion. 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Rob Reynolds commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Actually, I thought a bit more about a use case - You would want this is if you are RDPing into the box and causing a Puppet agent run or puppet apply. 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Rob Reynolds commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode I created this ticket for a discussion point. Given this command looks like it is for RDP (Terminal Services) only, and Puppet executes locally, I think we can safely close this as Won't Fix because it is not necessary. 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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title
Rob Reynolds created an issue
Puppet / PUP-3979
Windows Package Should Switch between Execute and Install Mode
Issue Type:
New Feature
Assignee:
Kylo Ginsberg
Components:
Types and Providers, Windows
Created:
2015/02/08 6:45 AM
Labels:
windows
Priority:
Normal
Reporter:
Rob Reynolds
From ServerFault:
The scenario is installing Windows applications with Puppet on a Windows RDP server. I have Puppet install the applications without problem, but per the best practice, you're supposed to be in install mode when doing so, and switching back to execute mode.
I can do the following and it works:
package {'Adobe AIR':
Jira (PUP-2551) Certname must be lowercase error not helpful
Title: Message Title Daniele Sluijters commented on PUP-2551 Re: Certname must be lowercase error not helpful "Due to an implementation detail in the current CA, all certificate names must be fully lower case". No one wants to know what the implementation detail is, they just want to know how to deal with it. 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.
