fiddyspence

[root@master2 ntp]# cat foo.pp

class { 'ntp': foo => false }
include ntp
[root@master2 ntp]# puppet apply foo.pp
Notice: Compiled catalog for master2 in environment production in 1.28 seconds
Notice: Finished catalog run in 0.89 seconds
[root@master2 ntp]# vi foo.pp
[root@master2 ntp]# cat foo.pp
include ntp

fiddyspence

[root@master2 ~]# puppet apply foo.pp
Notice: Compiled catalog for master2 in environment production in 0.24 seconds
Notice: sdkjfbkjsbd
Notice: /Stage[main]/Bar/Notify[sdkjfbkjsbd]/message: defined 'message' as 'sdkjfbkjsbd'
Notice: /Stage[main]/Foo/File[/tmp/file]/ensure: defined content as '{md5}d111ae55ded9fb2cd63c590d1d0b1b30'
Notice: Finished catalog run in 0.46 seconds
[root@master2 ~]# cat foo.pp
class foo ($content) {
  file{ '/tmp/file':
    content => $content,

fiddyspence

class foo {
  notify { 'foo': }
}

# this will be fine
include foo
include foo
include foo
include foo

fiddyspence

http://projects.puppetlabs.com/issues/8040

http://www.devco.net/archives/2012/12/13/simple-puppet-module-structure-redux.php

class foo ( $docroot ) {

  validate_absolute_path($docroot)

  class { '::mysql::server':
    root_password    => 'strongpassword',

fiddyspence

The Atlassian terms allow companies to access 1-to-1 chat history (for future chats, not retroactively). The Atlassian Privacy Policy also removes a HipChat restriction that has caused a lot of confusion for business customers. Under HipChat's support documentation (which is referenced in the HipChat privacy policy), HipChat administrators cannot view other users' 1-to-1 chat history or the files that were shared. In many cases, this is inconsistent with an employer's policy about employee communications occurring in the workplace, which employers typically have the right to access. Under the Atlassian Privacy Policy, HipChat administrators will have the right to access all information in the HipChat accounts they manage, including 1-to-1 chat history and files shared in those 1-to-1 chats. The HipChat Specific Terms require customers (e.g. the account holder) to secure all required consents from users to allow for this level of access. Note that this change does not apply retroactively; 1-to-1 chats occurrin

fiddyspence

spenceware:~ fids$ irb
irb(main):001:0> 'www.foo' =~ /^www.*/
=> 0

fiddyspence

ruby 1.9.3p448 (2013-06-27) [i386-mingw32]

C:\Program Files (x86)\Puppet Labs\Puppet\bin>facter domain
Could not retrieve domain: undefined method `gsub' for nil:NilClass
The system cannot find the path specified.
The system cannot find the path specified.
Using Facter::Util::Resolution.exec with a shell built-in is deprecated. Most bu
ilt-ins can be replaced with native ruby commands. If you really have to run a b
uilt-in, pass "cmd /c your_builtin" as a command (command responsible for this m
essage was "dnsdomainname 2> /dev/null")

fiddyspence

class thing {
  create_resources (foo,{})
  create_resources (bar,{})
  Foo <| tag == 'thing' |> -> Bar <| tag == 'thing' |>
}

fiddyspence

function ssh {
  while true ; do
    /usr/bin/ssh -A $*
    if [ $? == '0' ]; then
      break
    fi
    sleep 1
  done
}

fiddyspence

### Keybase proof

I hereby claim:

  * I am fiddyspence on github.
  * I am fiddyspence (https://keybase.io/fiddyspence) on keybase.
  * I have a public key whose fingerprint is C906 E87D 8922 519F F1F5  E0D9 7416 7B31 A1DA FABE

To claim this, I am signing this object: