This is the home of the InSpec AWS resource documentation found on https://docs.chef.io/inspec/resources/#aws.
We use Hugo to incorporate documentation from this repository into chef/chef-web-docs
and deploy it on https://docs.chef.io.
All resource pages are located in docs-chef-io/content/inspec/resources/
.
Make a new resource page by running hugo new -k resource inspec/resources/RESOURCE_NAME.md
from the docs-chef-io
directory.
You can also create a new page by duplicating an old page and then update the new page with content relevant to the new resource.
See our style guide for suggestions on writing documentation.
At the top of each resource is a block of front matter, which Hugo uses to add a title to each page and locate each page in the left navigation menu in <docs.chef.io>. Below is an example of a page's front matter:
+++
title = "RESOURCE NAME resource"
platform = "aws"
gh_repo = "inspec-aws"
[menu.inspec]
title = "RESOURCE NAME"
identifier = "inspec/resources/aws/RESOURCE NAME"
parent = "inspec/resources/aws"
+++
title
is the page title.
platform = aws
sorts each page into the correct category in the Chef InSpec resources list page.
gh_repo = "inspec-aws"
adds an "[edit on GitHub]" link to the top of each page that links to the Markdown page in the inspec/inspec-aws repository.
[menu.inspec]
places the page in the Chef InSpec section of the left navigation menu in <docs.chef.io>. All the parameters following this configure the link in the left navigation menu to the page.
title
is the title of page in the Chef InSpec menu.
identifier
is the identifier for a page in the menu. It should formatted like this: inspec/resources/aws/resource name
.
parent = "inspec/resources/aws"
is the identifier for the section of the menu that the page will be found in. This value is set in the chef-web-docs menu config.
A shortcode is a file with a block of text that can be added in multiple places in our documentation by referencing the shortcode file name.
This documentation set has three shortcodes located in the docs-chef-io/layouts/shortcodes
directory:
- inspec_filter_table.md
- aws_permissions_principal.md
- inspec_aws_install.md
Add a shortcode to a resource page by wrapping the filename, without the .md
file suffix, in double curly braces and percent symbols. For example: {{% inspec_filter_table %}}
.
The aws_permissions_principal
shortcode requires an action
parameter, which is the action that the AWS principal will need Effect
set to Allow
. For example, the AWS IAM Role resource page has:
{{% aws_permissions_principal action="IAM:Client:GetRoleResponse" %}}
which will render the following text:
Your Principal will need the
IAM:Client:GetRoleResponse
action withEffect
set toAllow
.
The chef/chef-web-docs repository uses the release-dates.json
file in docs-chef-io/assets/release-notes/inspec-aws
to generate release notes on https://docs.chef.io/release_notes_inspec_aws/. See below for more information on release notes for inspec-aws.
We use Hugo modules to build Chef's documentation from multiple repositories.
When release notes are announced for inspec-aws, the documentation for inspec-aws is updated at the same time. See the section below on release notes.
A member of the Docs Team can also update the inspec-aws resource documentation at any time when new resources are ready to be added to <docs.chef.io>.
We use Hugo, Go, andNPM to build the Chef Documentation website. You will need Hugo 0.93.1 or higher installed and running to build and view our documentation.
To install Hugo, NPM, and Go on Windows and macOS:
- On macOS run:
brew install hugo node go
- On Windows run:
choco install hugo nodejs golang -y
To install Hugo on Linux, run:
apt install -y build-essential
snap install node --classic --channel=12
snap install hugo --channel=extended
Run make serve
to build a local preview of the InSpec AWS resource documentation.
This will clone a copy of chef/chef-web-docs
into the docs-chef-io
directory.
That copy will be configured to build the InSpec AWS resource documentation from the docs-chef-io
directory
and live reload if any changes are made while the Hugo server is running.
- Run
make serve
- go to http://localhost:1313/inspec/resources/#aws
Run make clean_all
to delete the cloned copy of chef/chef-web-docs.
The process for publishing and announcing release notes for inspec-aws is mostly manual.
Edit the Pending Release Notes file in the inspec-aws wiki.
We recommend editing this page as new resources are added or changes are made to the inspec-aws resources.
Have a member of the documentation team review the Pending Release Notes file before they're released.
-
Log in to the chef-cd S3 account using saml2aws.
-
Run the
publish-release-notes.sh
script intools/release-notes
. You can run this from the Makefile withmake publish_release_notes
This will push the pending release notes to the S3 chef-cd bucket, reset the Pending Release Notes file, and update the
release-dates.json
file inassets/release-notes/inspec-aws
. -
Push up and merge a branch to
inspec/inspec-aws
with the changes made to therelease-dates.json
file.
chef-web-docs is configured to open a PR that will update the inspec-aws content on <doc.chef.io> when a change is committed to the release-dates.json
file in the inspec-aws repository. This will update the InSpec AWS resource documentation and update release notes for InSpec AWS resources.
A member fo the documentation team can merge that PR for you as soon as it's made.
Copy the release notes to a new announcement in Chef Release Announcements on Discourse.
You can find the proper release notes in the Pending Release Notes file history or on https://packages.chef.io/release-notes/inspec-aws/RELEASE_DATE.md
If you need support, contact Chef Support.
GitHub issues
Submit an issue to the inspec-aws repo for "important" documentation bugs that may need visibility among a larger group, especially in situations where a documentation bug may also surface a product bug.
Submit an issue to chef-web-docs for documentation feature requests and minor documentation issues.