Skip to content

Instantly share code, notes, and snippets.

Jennifer Davis iennae

Block or report user

Report or block iennae

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
iennae / gist:f4fcdfa395f4e36a8e4e4a81e00acf8e
Created May 28, 2018
chef-shell with chef-zero in local development
View gist:f4fcdfa395f4e36a8e4e4a81e00acf8e
kitchen login
cd /tmp/kitchen
/opt/chef/embedded/bin/chef-zero -d
sudo knife cookbook upload -a -c client.rb
sudo chef-shell -z -c client.rb -j /tmp/kitchen/dna.json

Keybase proof

I hereby claim:

  • I am iennae on github.
  • I am sigje ( on keybase.
  • I have a public key ASDf9k0bZKFrxayP12yFDYqp-dQ5AN1cRsqZEKDJDkybxAo

To claim this, I am signing this object:


Google Map

Recommendations from @clairemcquin

  • Chilaquiles at Senor Moose
  • Milkshakes at Luna Park
  • Tacos Chukis
  • All the ice cream at Full Tilt
  • Cheap teriyaki for take out
  • annapurna
  • little uncle
iennae /
Created May 13, 2016 — forked from lamont-granquist/
Three Ways to Write Correct Chef Resources

12.5 style custom resources

This is by far the most recommended way of writing resources for all users. There are two gotchas which we're working through:

  1. For helper functions that you used to write in your provider code or used to mixin to your provider code, you have to use an action_class do ... end block.
  2. The 12.5 resources allow for a shorthand notation in provider code where you can refer to properties by their bare name my_property and it works most of the time. Since it does not work all the time (because of the way ruby scopes things), its recommended to stick to referring to properties by new_resource.my_property.

You cannot subclass, and must use mixins for code-sharing (which is really a best practice anyway -- e.g. see languages like rust which do not support subclassing).

in resources/whatever.rb:

  • Concrete, transparent, measurable plan to increase the number of underrepresented population in engineering roles and engineering leadership roles.
  • Interview only if there are more than 2 underrepresented population in the interview pool for this position.
  • Friendly atmosphere where collaboration and mentorship is encouraged and supported.
  • Commitment to respectful conflict practices.
  • Meaningful work with clear linkage between work and company goals.
  • Demonstrated commitment to ethical business practices, e.g. B corp certification.
  • Commitment to career development including yearly conferences and education.
  • Commitment to work/life integration and flexibility; e.g. 40-45 hrs/week.
  • Commitment to contributing, supporting and using open source.
You can’t perform that action at this time.