Commit ad24ee3d authored by Jamie Tanna's avatar Jamie Tanna

Use Chef logo for Chef-related article previews

Logo via https://brand.chef.io/chef-corporate/#logos

Closes #226.
parent 2cdfea76
Pipeline #19898490 passed with stages
in 13 minutes and 32 seconds
......@@ -4,6 +4,7 @@ title: Building Chef Cookbooks with GitLab (Part 1)
description: An introduction to how to build a cookbook using GitLab's Continuous Integration platform in conjunction with `kitchen-docker`.
categories: guide chef gitlab
tags: howto findings gitlab chef test-kitchen docker gitlab-ci
image: /assets/img/vendor/chef-logo.png
---
## Foreword
......
......@@ -4,6 +4,7 @@ title: 'Testing `include_recipe`s with Chef and ChefSpec'
description: How to best test `include_recipe`s within your Chef recipes, as well as how to ensure that you aren't running any dependent recipes in your tests.
categories: findings
tags: findings chef tdd chefspec
image: /assets/img/vendor/chef-logo.png
---
While writing cookbooks, both personally and professionally, I practice a heavy use of TDD to ensure that the recipes are doing what I expect them to. As part of this, I will want to test both standard resources, as well as `include_recipe`s:
......
......@@ -5,6 +5,7 @@ description: How to handle getting an `EACCES` when trying to run ChefSpec on a
categories: findings
tags: findings chef chefspec chefdk
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
You may find that when running ChefSpec on your Chef cookbook, you may hit an error such as the following, spouting `Permission denied`:
......
......@@ -5,6 +5,7 @@ description: How to get the ChefDK (and associated tools) to trust internal / se
categories: findings chef
tags: chef chefdk certificates berkshelf
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
If you're writing Chef cookbooks in a corporate environment, you may be developing against services on your internal network. As the services are not going to be exposed externally, the certificate used for HTTPS will be an intranet-only/self-signed cert, and therefore will require you to manually add it to your trust store.
......
......@@ -4,6 +4,7 @@ title: 'Running `service` resources in Kitchen-Docker'
description: How to get up and running with `service` resources when running Test Kitchen with the Docker driver, in this example for use with GitLab CI.
categories: findings chef kitchen docker
tags: findings chef kitchen docker howto
image: /assets/img/vendor/chef-logo.png
---
When writing cookbooks, you need to actually test that they work. This is often done using [Test Kitchen][test-kitchen], a tool that allows you to converge your cookbooks on a real machine. There are a number of drivers that can be used, such as [kitchen-vagrant][kitchen-vagrant] and [kitchen-docker][kitchen-docker].
......
......@@ -5,6 +5,7 @@ description: 'Getting around the pesky `OpenSSL::SSL::SSLError SSLv2/v3 read ser
categories: findings
tags: chef findings proxy cli shell chefdk berkshelf
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
I found recently that when trying to download cookbooks in an environment that required a proxy, I would encounter the error `OpenSSL::SSL::SSLError: SSL_connect SYSCALL returned=5 errorno=0 state=SSLv2/v3 read server hello A`, even when I had a proxy set for i.e. `.example.com`:
......
......@@ -4,6 +4,7 @@ description: 'How to resolve the `Parenthesize the param lazy` Rubocop error whe
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-rubocop chef rubocop chef-13 rubocop-0-49
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -4,6 +4,7 @@ description: 'How to resolve the `Parenthesize the param render_file` Rubocop er
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-chefspec chef chefspec
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -4,6 +4,7 @@ description: 'Replace your `block.old_run_action` with `block.block.call` to tri
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-chefspec chef chefspec chef-13 chefspec-7
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -4,6 +4,7 @@ description: 'Notes on the main problems encountered when upgrading from Chef 12
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-rubocop chef-13-upgrade-chefspec chef rubocop chefspec chef-13 chefspec-7 rubocop-0-49
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
I've recently been working through upgrading my Chef 12 cookbooks to Chef 13, as Chef 12 is to be [End of Life'd in April 2018][chef-12-eol].
......
......@@ -4,6 +4,7 @@ description: 'A one-liner shell command to fix Rubocop errors `%w-literals shoul
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-rubocop chef rubocop chef-13 rubocop-0-49
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -4,6 +4,7 @@ description: 'Preparing for breaking changes in Chef 14 by renaming `property_na
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef-13-upgrade-deprecation chef chef-13 chef-14
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
In Chef 12 and Chef 13, the following code would work, allowing the `file` resource to access the `my_content` property:
......
......@@ -4,6 +4,7 @@ description: 'Fixing odd `Logger` entries in autogenerated `knife-cookbook-doc`
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef knife-cookbook-doc chef-13 documentation
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -3,6 +3,7 @@ title: "Testing Chef's `ruby_block`s with ChefSpec"
description: 'Testing implementation of a `ruby_block` in ChefSpec, to ensure that the code executes as expected'
categories: findings chef
tags: findings chef chefspec testing
image: /assets/img/vendor/chef-logo.png
---
I like to ensure that all my code is as well unit tested as possible, both so I can quickly iterate changes, and to ensure that future changes don't inadvertently break functionality.
......
......@@ -4,6 +4,7 @@ description: 'Disabling the `Missing space after #` and `Do not use block commen
categories: findings chef-13-upgrade
tags: findings chef-13-upgrade chef knife-cookbook-doc chef-13 documentation chef-13-upgrade-rubocop
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
{% include posts/chef-13/intro.html %}
......
......@@ -5,6 +5,7 @@ description: 'Hitting the error `permission denied while trying to connect to th
categories: findings
tags: docker chef findings
no_toc: true
image: /assets/img/vendor/chef-logo.png
---
Yesterday I was writing a cookbook, where I needed to log in to GitLab's private registry:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment