I didn't even realize this thread was old. Oops. I saw it come across
email but I guess its how my email reader works.
On Friday, March 27, 2015 at 12:00:22 PM UTC-7, Trevor Vaughan wrote:
>
> Wow, thread resurrection!
>
> I figured out how to solve my problem but thanks for the pointers to the
Wow, thread resurrection!
I figured out how to solve my problem but thanks for the pointers to the
additional tools, quite useful.
I also ended up dumping variables either through Pry or through a function.
The issue that I was having is that I have some functions that modify items
on the filesy
Coming from regular language testing your first thought with puppet is how
do I control the flow of code when testing. In normal languages you can
mock the functions, getters, setters and possibly instance variables. With
puppet its a bit different.
You can control the flow of puppet code onl
On Fri, Mar 27, 2015 at 9:26 AM, Josh Pederson
wrote:
> For folks who utilize cloud environments (AWS, OpenStack, Azure, etc) in
> your day-to-day continuous delivery (CD) and/or application deploys I'd
> really appreciate any description of how you use Puppet in your process.
>
> Some of the que
>
> [snip]
> >
> > Environment variables vs configuration via a file
> >
> > Dominic Cleal indicated that we should change the SELinux context before
> > we read any configuration files, which makes us need an alternate method
> > of configuring SELinux, which the reason of running unconfined
On 03/27/2015 05:26 PM, Josh Pederson wrote:
> For folks who utilize cloud environments (AWS, OpenStack, Azure, etc) in
> your day-to-day continuous delivery (CD) and/or application deploys I'd
> really appreciate any description of how you use Puppet in your process.
Hi,
I think you definitely w
For folks who utilize cloud environments (AWS, OpenStack, Azure, etc) in
your day-to-day continuous delivery (CD) and/or application deploys I'd
really appreciate any description of how you use Puppet in your process.
Some of the questions I'm curious about:
- How do you provision new cloud
>
> Just out of curiosity, are you going to double wrap this in a Java
> Security Policy for those systems that don't have SELinux?
>
IFAIK JSP and SELinux are two different technologies with different goals.
JSP can't protect you from security bugs in JVM and the granulality is much
lower than sy
Just out of curiosity, are you going to double wrap this in a Java Security
Policy for those systems that don't have SELinux?
Thanks,
Trevor
On Fri, Mar 27, 2015 at 5:49 AM, Dominic Cleal wrote:
> On 26/03/15 19:25, Melissa Stone wrote:
> > Hi all,
> >
> > I just wanted to point out that Adrie
On 26/03/15 19:25, Melissa Stone wrote:
> Hi all,
>
> I just wanted to point out that Adrien brought up some interesting
> comments in the ticket for this discussion. So that response gets more
> exposure, I wanted to post it here:
>
> From Adrien Thebo:
>
> I've reviewed PR 3627 and the puppet-
10 matches
Mail list logo
