override_attributes
|
-Optional. A set of attributes to be applied to all nodes, even if the node already has a value for an attribute. This is useful for ensuring that certain attributes always have specific values. If more than one role attempts to set an override value for the same attribute, the last role applied wins. When nested attributes are present, they are preserved. For example:
+ | Optional. A set of attributes to be applied to all nodes, even if the node already has a value for an attribute. This is useful for ensuring that certain attributes always have specific values. If more than one role attempts to set an override value for the same attribute, the last role applied wins. When nested attributes are present, they're preserved. For example:
override_attributes 'apache2' => { 'max_children' => '50' }
The parameters in a Ruby file are actually Ruby method calls, so parentheses can be used to provide clarity when specifying numerous or deeply-nested attributes. For example:
override_attributes(
@@ -196,7 +196,7 @@ cookbook_versions({
Attributes are optional and can be set at the default and override
levels. These will be processed according to attribute precedence. An
environment attribute will be applied to all nodes within the
-environment, except in places where it is overridden by an attribute
+environment, except in places where it's overridden by an attribute
with higher precedence. For example:
```ruby
@@ -288,7 +288,7 @@ Once created, an environment can be managed in several ways:
control system. These files are pushed to the Chef Infra Server
using the `knife environment` subcommand and the `from file`
argument. This approach allows environment data to be dynamically
- generated. This approach will not work unless these files are
+ generated. This approach won't work unless these files are
defined in the proper format---Ruby file end with `.rb`; JSON files
end with `.json`.
@@ -323,7 +323,7 @@ be used to store environment data within a data bag: by using a
top-level key that corresponds to the environment or by using separate
items for each environment.
-A data bag that is storing a top-level key for an environment might look
+A data bag that's storing a top-level key for an environment might look
something like this:
```json
@@ -359,7 +359,7 @@ Environment attributes that are used with roles can be overridden.
Typically, this is done by using attribute precedence, but sometimes it
may be necessary to ensure that specific attributes are used based on
the presence of specific environments. This type of scenario is best
-addressed in using a recipe that relies on a top-level key that is
+addressed in using a recipe that relies on a top-level key that's
stored in a data bag.
For example, to retrieve a value from a data bag based on a specific
@@ -374,8 +374,8 @@ attribute_i_want = mything[node.chef_environment]
A node is considered to be associated with an environment when the
`chef_environment` attribute is set. The `chef_environment` attribute
-cannot be set with normal or override attributes (in a role)
-because it is actually a method. An environment may be set explicitly
+can't be set with normal or override attributes (in a role)
+because it's actually a method. An environment may be set explicitly
using the following methods:
- By using the `knife edit` and `knife exec` subcommands
diff --git a/content/errors.md b/content/errors.md
index 1dd8858ecb..3be5334c92 100644
--- a/content/errors.md
+++ b/content/errors.md
@@ -49,7 +49,7 @@ FATAL: Net::HTTPClientException: 401 "Unauthorized"
## Failed to authenticate to
-When the values for certain settings in the client.rb file---`node_name` and `client_key`---are incorrect, it will not be possible to authenticate to the Chef Infra Server. An error similar to the following is shown:
+When the values for certain settings in the client.rb file---`node_name` and `client_key`---are incorrect, it won't be possible to authenticate to the Chef Infra Server. An error similar to the following is shown:
```bash
ERROR: Failed to authenticate to https://api.opscode.com/organizations/ORGANIZATION as USERNAME with key /path/to/USERNAME.pem
@@ -169,7 +169,7 @@ DEBUG: Sending HTTP Request to https://api.opscode.com/organizations/ORGNAME/nod
ERROR: Running exception handlers
```
-The URL will help identify the type of permission issue. If the URL is an index action (that is, operating on a collection of resources, like `/nodes`) then this is a global permission. If the URL is operating on an instance of a collection (`/nodes/NODENAME`) then this is an object permission issue.
+The URL will help identify the type of permission issue. If the URL is an index action (that's, operating on a collection of resources, like `/nodes`) then this is a global permission. If the URL is operating on an instance of a collection (`/nodes/NODENAME`) then this is an object permission issue.
To fix the global permissions:
@@ -185,7 +185,7 @@ To fix object permissions:
1. Log in to the Chef management console and click on the failing object type (most likely **Nodes**).
-2. Click on the object in the list that is causing the error.
+2. Click on the object in the list that's causing the error.
3. Click on the **Permissions** sub-tab. Which permission it needs, depends on the type of request that failed:
@@ -238,10 +238,10 @@ If you're seeing an error like:
Client key /etc/chef/client.pem isn'tresent - registering
WARN: Failed to read the private key /etc/che/validation.pem: #
FATAL: Stacktrace dumped to /etc/chef/cache/chef-stacktrace.out
-FATAL: Chef::Exceptions::PrivateKeyMissing: I cannot read /etc/chef/validation.pem, which you told me to use to sign requests
+FATAL: Chef::Exceptions::PrivateKeyMissing: I can't read /etc/chef/validation.pem, which you told me to use to sign requests
```
-It means that Chef Infra Client could not find your validation.pem.
+It means that Chef Infra Client couldn't find your validation.pem.
#### Troubleshooting steps
@@ -271,7 +271,7 @@ git commit -am "Updating so I can install a site cookbook"
Re-run the `knife supermarket install` subcommand again to install the community cookbook.
-### Cannot find config file
+### Can't find config file
If you're seeing an error like:
@@ -280,7 +280,7 @@ WARN: ***************************************
WARN: Can not find config file: /etc/chef/client.rb, using defaults.
WARN: No such file or directory - /etc/chef/client.rb
# ... output truncated ... #
-FATAL: Chef::Exceptions::PrivateKeyMissing: I cannot read /etc/chef/validation.pem, which you told me to use to sign requests!
+FATAL: Chef::Exceptions::PrivateKeyMissing: I can't read /etc/chef/validation.pem, which you told me to use to sign requests!
```
#### Troubleshooting steps
@@ -335,11 +335,11 @@ Upgrading isn't supported at this time.
- Back up the data using `knife ec backup`, create a new backend instance, and then restore the data
- Re-point frontend machines at the new backend instance **or** assign the new backend instance the name/VIP of the old backend instance (including certificates and keys)
-### CSPG010 (cannot connect)
+### CSPG010 (can't connect)
#### Reason
-Cannot connect to PostgreSQL on the remote server.
+Can't connect to PostgreSQL on the remote server.
#### Possible causes
@@ -348,11 +348,11 @@ Cannot connect to PostgreSQL on the remote server.
- Network routing configuration is preventing access to the host
- When using Amazon Web Services (AWS), rules for security groups are preventing the Chef Infra Server from communicating with PostgreSQL
-### CSPG011 (cannot authenticate)
+### CSPG011 (can't authenticate)
#### Reason
-Cannot authenticate to PostgreSQL on the remote server.
+Can't authenticate to PostgreSQL on the remote server.
#### Possible causes
@@ -363,7 +363,7 @@ Cannot authenticate to PostgreSQL on the remote server.
#### Reason
-Cannot connect to PostgreSQL on the remote server because rules in
+Can't connect to PostgreSQL on the remote server because rules in
`pg_hba` are incorrect.
#### Possible causes
diff --git a/content/feedback.md b/content/feedback.md
index 156171486f..19aca7819a 100644
--- a/content/feedback.md
+++ b/content/feedback.md
@@ -14,7 +14,7 @@ product = []
+++
chef-docs hopes that the documentation is always just what you are
-looking for, but when that is not the case we do appreciate
+looking for, but when that isn't the case we do appreciate
feedback. There are several ways to get feedback to chef-docs. For
members of the Chef community, customers, or people who just want to
send feedback, choose any of the following options:
@@ -28,7 +28,7 @@ suggestions for improving the documentation on a page. Be as detailed as possibl
Use the feedback form at the bottom of this page for submitting general feedback
about Chef's documentation.
-These forms are not for customer support. If you need support,
+These forms aren't for customer support. If you need support,
contact [Chef support](https://supportlink.chef.io/).
## Email
diff --git a/content/fips.md b/content/fips.md
index 1a1385264f..8dd0805bed 100644
--- a/content/fips.md
+++ b/content/fips.md
@@ -13,7 +13,7 @@ product = ["client", "server", "workstation"]
weight = 30
+++
-## What is FIPS?
+## What's FIPS?
Federal Information Processing Standards (FIPS) are federal standards
for computer systems used by contractors of government agencies and
@@ -26,26 +26,26 @@ cryptographic modules under the FIPS 140-2 standard. The OpenSSL Object
Module provides an API for invoking FIPS approved cryptographic
functions from calling applications.
-### Who Should Enable FIPS?
+### Who should enable FIPS?
You may be legally required to enable FIPS if you are a United States
non-military government agency, or are contracting with one. If you are
not sure if you need to enable FIPS, please check with your compliance
department.
-### Who Should Not Enable FIPS?
+### Who shouldn't enable FIPS?
You will only need to enable FIPS if you are a US non-military
government agency, or contracting with one, and you are contractually
-obligated to meet federal government security standards. If you are not
-a US non-military governmental agency, or you are not contracting with
-one, and you are not contractually obligated to meet federal government
-security standards, then do not enable FIPS. Chef products have robust
+obligated to meet federal government security standards. If you aren't
+a US non-military governmental agency, or you aren't contracting with
+one, and you aren't contractually obligated to meet federal government
+security standards, then don't enable FIPS. Chef products have robust
security standards even without FIPS, and FIPS prevents the use of
certain hashing algorithms you might want to use, so we only recommend
-enabling FIPS if it is contractually necessary.
+enabling FIPS if it's contractually necessary.
-## Supported Products
+## Supported products
**Supported:**
@@ -55,11 +55,11 @@ enabling FIPS if it is contractually necessary.
**Unsupported:**
-FIPS mode is not supported for Chef Infra Server add-ons. This includes Chef Manage.
+FIPS mode isn't supported for Chef Infra Server add-ons. This includes Chef Manage.
-## How to Enable FIPS Mode in the Operating System
+## How to enable FIPS mode in the operating system
-### FIPS Kernel Settings
+### FIPS kernel settings
Windows and Red Hat Enterprise Linux can both be configured for FIPS
mode using a kernel-level setting. After FIPS mode is enabled at the
@@ -82,7 +82,7 @@ To enable FIPS on your platform follow these instructions:
- [Windows](https://technet.microsoft.com/en-us/library/cc750357.aspx)
- [Ubuntu](https://security-certs.docs.ubuntu.com/en/fips)
-## How to Enable FIPS Mode for the Chef Infra Server
+## How to enable FIPS mode for Chef Infra Server
### Prerequisites
@@ -92,14 +92,14 @@ To enable FIPS on your platform follow these instructions:
### Configuration
If you have FIPS compliance enabled at the kernel level and install or
-reconfigure the Chef Infra Server then it will default to running in
+reconfigure Chef Infra Server then it will default to running in
FIPS mode.
-To enable FIPS manually for the Chef Infra Server, can add `fips true`
+To enable FIPS manually for Chef Infra Server, can add `fips true`
to the `/etc/opscode/chef-server.rb` and reconfigure. For more
configuration information see [chef-server.rb Optional Settings](/server/config_rb_server_optional_settings/).
-## How to Enable FIPS Mode for the Chef Infra Client
+## How to enable FIPS mode for Chef Infra Client
### Prerequisites
@@ -110,6 +110,6 @@ configuration information see [chef-server.rb Optional Settings](/server/config_
If you have FIPS compliance enabled at the kernel level, Chef Infra Client will default to running in FIPS mode. Otherwise, add `fips true` to the `/etc/chef/client.rb` or `C:\\chef\\client.rb`.
-#### Bootstrap a Node Using FIPS
+#### Bootstrap a node using FIPS
{{< readfile file="content/workstation/reusable/md/knife_bootstrap_node_fips.md" >}}
diff --git a/content/glossary.md b/content/glossary.md
index 119613f55f..1add86fccb 100644
--- a/content/glossary.md
+++ b/content/glossary.md
@@ -34,11 +34,11 @@ Chef Automate
Chef Infra Client
-: A command-line tool that that runs Chef. Also, the name of Chef as it is installed on a node.
+: A command-line tool that that runs Chef. Also, the name of Chef as it's installed on a node.
Chef Infra Server
-: The Chef Infra Server acts as a hub for configuration data. The Chef Infra Server stores cookbooks, the policies that are applied to nodes, and metadata that describes each registered node that is being managed by Chef Infra Client. Nodes use Chef Infra Client to ask the Chef Infra Server for configuration details, such as recipes, templates, and file distributions.
+: The Chef Infra Server acts as a hub for configuration data. The Chef Infra Server stores cookbooks, the policies that are applied to nodes, and metadata that describes each registered node that's being managed by Chef Infra Client. Nodes use Chef Infra Client to ask the Chef Infra Server for configuration details, such as recipes, templates, and file distributions.
Chef Workstation
@@ -70,7 +70,7 @@ custom resource
data bag
-: A data_bag is a global variable that is stored as JSON data and is accessible from a Chef Infra Server.
+: A data_bag is a global variable that's stored as JSON data and is accessible from a Chef Infra Server.
environment
@@ -90,15 +90,15 @@ library
node
-: A node is any physical, virtual, or cloud device that is configured and maintained by an instance of Chef Infra Client.
+: A node is any physical, virtual, or cloud device that's configured and maintained by an instance of Chef Infra Client.
node object
-: A node object is a history of the attributes, run-lists, and roles that were used to configure a node that is under management by Chef Infra.
+: A node object is a history of the attributes, run-lists, and roles that were used to configure a node that's under management by Chef Infra.
ohai
-: Ohai is a tool that is used to detect attributes on a node, and then provide these attributes to Chef Infra Client at the start of every run.
+: Ohai is a tool that's used to detect attributes on a node, and then provide these attributes to Chef Infra Client at the start of every run.
organization
@@ -122,12 +122,12 @@ role
run-list
-: A run-list defines all of the configuration settings that are necessary for a node that is under management by Chef to be put into the desired state and the order in which these configuration settings are applied.
+: A run-list defines all of the configuration settings that are necessary for a node that's under management by Chef to be put into the desired state and the order in which these configuration settings are applied.
Test Kitchen
-: Test Kitchen is an integration framework that is used to automatically test cookbook data across any combination of platforms and test suites. Test Kitchen is packaged in Chef Workstation.
+: Test Kitchen is an integration framework that's used to automatically test cookbook data across any combination of platforms and test suites. Test Kitchen is packaged in Chef Workstation.
Unified Mode
-: Unified mode combines the compile and converge stages of the Chef Infra Client run into one phase. Unified mode means that the Chef Infra Client compiles and applies a custom resource in order, from top to bottom. Unified mode works only on custom resources and does not affect other resources or recipes.
+: Unified mode combines the compile and converge stages of the Chef Infra Client run into one phase. Unified mode means that the Chef Infra Client compiles and applies a custom resource in order, from top to bottom. Unified mode works only on custom resources and doesn't affect other resources or recipes.
diff --git a/content/google.md b/content/google.md
index 8f8a092b6d..eb1f19e91e 100644
--- a/content/google.md
+++ b/content/google.md
@@ -40,7 +40,7 @@ Cloud SDK](https://cloud.google.com/sdk/) and run the
`gcloud auth application-default login` command, which will create the
credentials file for you.
-If you already have a file you'd like to use that is in a different
+If you already have a file you'd like to use that's in a different
location, set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable
with the full path to that file.
diff --git a/content/habitat/habitat_cli.md b/content/habitat/habitat_cli.md
index 21a2db7258..4876882cee 100644
--- a/content/habitat/habitat_cli.md
+++ b/content/habitat/habitat_cli.md
@@ -18,7 +18,7 @@ The commands for the Chef Habitat CLI (`hab`) are listed below.
| Applies to Version | Last Updated |
| ------- | ------------ |
-| hab 1.6.1041/20240411141804 (linux) | 11 Apr 2024 |
+| hab 1.6.1243/20241227194506 (linux) | 27 Dec 2024 |
## hab
@@ -96,7 +96,7 @@ hab bldr
| Command | Description |
| ------- | ----------- |
| [hab bldr channel](#hab-bldr-channel) | Commands relating to Habitat Builder channels |
-| [hab bldr job](#hab-bldr-job) | Commands relating to Habitat Builder jobs |
+| [hab bldr job](#hab-bldr-job) | REMOVED: Commands relating to Habitat Builder jobs |
---
### hab bldr channel
@@ -306,7 +306,7 @@ hab bldr channel promote [OPTIONS] --origin
| Command | Description |
| ------- | ----------- |
-| [hab bldr job cancel](#hab-bldr-job-cancel) | Cancel a build job group and any in-progress builds |
-| [hab bldr job demote](#hab-bldr-job-demote) | Demote packages from a completed build job from a specified channel |
-| [hab bldr job promote](#hab-bldr-job-promote) | Promote packages from a completed build job to a specified channel |
-| [hab bldr job start](#hab-bldr-job-start) | Schedule a build job or group of jobs |
-| [hab bldr job status](#hab-bldr-job-status) | Get the status of one or more job groups |
+| [hab bldr job cancel](#hab-bldr-job-cancel) | REMOVED: Cancel a build job group and any in-progress builds |
+| [hab bldr job demote](#hab-bldr-job-demote) | REMOVED: Demote packages from a completed build job from a specified channel |
+| [hab bldr job promote](#hab-bldr-job-promote) | REMOVED: Promote packages from a completed build job to a specified channel |
+| [hab bldr job start](#hab-bldr-job-start) | REMOVED: Schedule a build job or group of jobs |
+| [hab bldr job status](#hab-bldr-job-status) | REMOVED: Get the status of one or more job groups |
---
### hab bldr job cancel
-Cancel a build job group and any in-progress builds
+REMOVED: Cancel a build job group and any in-progress builds
**USAGE**
@@ -372,7 +372,7 @@ hab bldr job cancel [FLAGS] [OPTIONS]
### hab bldr job demote
-Demote packages from a completed build job from a specified channel
+REMOVED: Demote packages from a completed build job from a specified channel
**USAGE**
@@ -409,7 +409,7 @@ hab bldr job demote [FLAGS] [OPTIONS]
### hab bldr job promote
-Promote packages from a completed build job to a specified channel
+REMOVED: Promote packages from a completed build job to a specified channel
**USAGE**
@@ -446,7 +446,7 @@ hab bldr job promote [FLAGS] [OPTIONS]
### hab bldr job start
-Schedule a build job or group of jobs
+REMOVED: Schedule a build job or group of jobs
**USAGE**
@@ -482,7 +482,7 @@ hab bldr job start [FLAGS] [OPTIONS] [PKG_TARGET]
### hab bldr job status
-Get the status of one or more job groups
+REMOVED: Get the status of one or more job groups
**USAGE**
@@ -1825,10 +1825,11 @@ hab pkg build [FLAGS] [OPTIONS]
**OPTIONS**
```
---cache-key-path Cache for creating and searching for encryption keys [env: HAB_CACHE_KEY_PATH=] [default: /hab/cache/keys]
--k, --keys Installs secret origin keys (ex: "unicorn", "acme,other,acme-ops")
--r, --root Sets the Studio root (default: /hab/studios/)
--s, --src Sets the source path (default: $PWD)
+--cache-key-path Cache for creating and searching for encryption keys [env: HAB_CACHE_KEY_PATH=] [default: /hab/cache/keys]
+-k, --keys Installs secret origin keys (ex: "unicorn", "acme,other,acme-ops")
+-r, --root Sets the Studio root (default: /hab/studios/)
+-f, --refresh-channel Channel used to retrieve plan dependencies for Chef supported origins env: HAB_REFRESH_CHANNEL=] [default: stable]
+-s, --src Sets the source path (default: $PWD)
```
**ARGS**
@@ -2245,6 +2246,7 @@ hab pkg install [FLAGS] [OPTIONS] ...
-b, --binlink Binlink all binaries from installed package(s) into BINLINK_DIR
-f, --force Overwrite existing binlinks
--ignore-install-hook Do not run any install hooks
+ --ignore-local Do not use locally-installed packages when a corresponding package cannot be installed from Builder
-h, --help Prints help information
-V, --version Prints version information
```
diff --git a/content/habitat/service_templates.md b/content/habitat/service_templates.md
index 4ed70c4360..a608bb85cd 100644
--- a/content/habitat/service_templates.md
+++ b/content/habitat/service_templates.md
@@ -1,7 +1,7 @@
+++
title = "Service Template Data"
-date = 2024-04-11T15:19:34.317Z
+date = 2024-12-27T20:47:49.689Z
draft = false
[menu]
diff --git a/content/handlers.md b/content/handlers.md
index a2e42464cb..7643971fe8 100644
--- a/content/handlers.md
+++ b/content/handlers.md
@@ -155,7 +155,7 @@ See the [chef_handler Resource]({{< relref "/resources/chef_handler">}}) documen
### Chef Infra Client
-Start handlers can be distributed using the **chef-client** cookbook, which will install the handler on the target node during the initial configuration of the node. This ensures that the start handler is always present on the node so that it is available to Chef Infra Client at the start of every run.
+Start handlers can be distributed using the **chef-client** cookbook, which will install the handler on the target node during the initial configuration of the node. This ensures that the start handler is always present on the node so that it's available to Chef Infra Client at the start of every run.
## Custom Handlers
@@ -169,7 +169,7 @@ A custom handler can be created to support any situation. The easiest way to bui
### Syntax
-The syntax for a handler can vary, depending on what the the situations the handler is being asked to track, the type of handler being used, and so on. All custom exception and report handlers are defined using Ruby and must be a subclass of the `Chef::Handler` class.
+The syntax for a handler can vary depending on what the situations the handler is being asked to track, for example the handler type being used. All custom exception and report handlers are defined using Ruby and must be a subclass of the `Chef::Handler` class.
```ruby
require 'chef/log'
@@ -187,8 +187,8 @@ where:
- `require` ensures that the logging functionality of Chef Infra Client is available to the handler
- `ModuleName` is the name of the module as it exists within the `Chef` library
-- `HandlerName` is the name of the handler as it is used in a recipe
-- `report` is an interface that is used to define the custom handler
+- `HandlerName` is the name of the handler as it's used in a recipe
+- `report` is an interface that's used to define the custom handler
For example, the following shows a custom handler that sends an email that contains the exception data when a Chef Infra Client run fails:
@@ -298,7 +298,7 @@ end
### Optional Interfaces
-The following interfaces may be used in a handler in the same way as the `report` interface to override the default handler behavior in Chef Infra Client. That said, the following interfaces are not typically used in a handler and, for the most part, are completely unnecessary for a handler to work properly and/or as desired.
+The following interfaces may be used in a handler in the same way as the `report` interface to override the default handler behavior in Chef Infra Client. That said, the following interfaces aren't typically used in a handler and, for the most part, are completely unnecessary for a handler to work properly and/or as desired.
#### data
@@ -378,7 +378,7 @@ The `run_status` object is initialized by Chef Infra Client before the `report`
`success?`
-: Show that a Chef Infra Client run succeeded when uncaught exceptions were not raised during a Chef Infra Client run. A report handler runs when the `success?` indicator is `true`.
+: Show that a Chef Infra Client run succeeded when uncaught exceptions weren't raised during a Chef Infra Client run. A report handler runs when the `success?` indicator is `true`.
`updated_resources`
@@ -386,7 +386,7 @@ The `run_status` object is initialized by Chef Infra Client before the `report`
{{< note >}}
-These properties are not always available. For example, a start handler runs at the beginning of Chef Infra Client run, which means that properties like `end_time` and `elapsed_time` are still unknown and will be unavailable to the `run_status` object.
+These properties aren't always available. For example, a start handler runs at the beginning of Chef Infra Client run, which means that properties like `end_time` and `elapsed_time` are still unknown and will be unavailable to the `run_status` object.
{{< /note >}}
diff --git a/content/infra_language/checking_hypervisors.md b/content/infra_language/checking_hypervisors.md
index 9201ca283d..cc830c4f79 100644
--- a/content/infra_language/checking_hypervisors.md
+++ b/content/infra_language/checking_hypervisors.md
@@ -23,7 +23,7 @@ Determine if the current node supports running guests under any virtualization e
## physical?
-Determine if the current node is NOT running under any virtualization environment (bare-metal or hypervisor on metal).
+Determine if the current node isn't running under any virtualization environment (bare-metal or hypervisor on metal).
## hyperv?
@@ -91,7 +91,7 @@ Determine if the current node is running as a vagrant guest.
## vagrant_key?
-Check if the `vagrant` key exists on the +node+ object. Note: This key is no longer populated by vagrant, but it is kept around for legacy purposes.
+Check if the `vagrant` key exists on the +node+ object. Note: This key is no longer populated by vagrant, but it's kept around for legacy purposes.
## vagrant_domain?
diff --git a/content/infra_language/checking_platforms.md b/content/infra_language/checking_platforms.md
index 94628b1fc8..1081a1894d 100644
--- a/content/infra_language/checking_platforms.md
+++ b/content/infra_language/checking_platforms.md
@@ -13,7 +13,7 @@ gh_repo = "chef-web-docs"
## platform?
-Use the `platform?` helper method to ensure that certain actions are run for specific platforms. The `platform?` method will return true if one of the listed parameters matches the `node['platform']` attribute that is detected by [Ohai](/ohai) during every Chef Infra Client run.
+Use the `platform?` helper method to ensure that certain actions are run for specific platforms. The `platform?` method will return true if one of the listed parameters matches the `node['platform']` attribute that's detected by [Ohai](/ohai) during every Chef Infra Client run.
The syntax for the `platform?` method is as follows:
@@ -24,7 +24,7 @@ platform?('parameter', 'parameter')
where:
- `parameter` is a comma-separated list, each specifying a platform, such as Red Hat, CentOS, or Fedora
-- `platform?` method is typically used with an `if`, `elsif`, or `case` statement that contains Ruby code that is specific for the platform, if detected
+- `platform?` method is typically used with an `if`, `elsif`, or `case` statement that contains Ruby code that's specific for the platform, if detected
### platform Values
@@ -208,7 +208,7 @@ platform_family?('parameter', 'parameter')
where:
- `'parameter'` is a comma-separated list, each specifying a platform family, such as Debian, or Red Hat Enterprise Linux
-- `platform_family?` method is typically used with an `if`, `elsif`, or `case` statement that contains Ruby code that is specific for the platform family, if detected
+- `platform_family?` method is typically used with an `if`, `elsif`, or `case` statement that contains Ruby code that's specific for the platform family, if detected
### platform_family Values
diff --git a/content/infra_language/cookbook_execution.md b/content/infra_language/cookbook_execution.md
index f4861c42b3..c35aaee470 100644
--- a/content/infra_language/cookbook_execution.md
+++ b/content/infra_language/cookbook_execution.md
@@ -94,7 +94,7 @@ where `file` is the type of resource, `/etc/hosts` is the name, and `f.mode` is
### attribute?
-Use the `attribute?` method to ensure that certain actions only execute in the presence of a particular node attribute. The `attribute?` method will return true if one of the listed node attributes matches a node attribute that is detected by Ohai during every Chef Infra Client run.
+Use the `attribute?` method to ensure that certain actions only execute in the presence of a particular node attribute. The `attribute?` method will return true if one of the listed node attributes matches a node attribute that's detected by Ohai during every Chef Infra Client run.
The syntax for the `attribute?` method is as follows:
@@ -106,7 +106,7 @@ For example:
```ruby
if node.attribute?('ipaddress')
- # the node has an ipaddress
+ # the node has an IP address
end
```
diff --git a/content/infra_language/editing_resources.md b/content/infra_language/editing_resources.md
index 4aa54b2587..8bbda6e505 100644
--- a/content/infra_language/editing_resources.md
+++ b/content/infra_language/editing_resources.md
@@ -23,8 +23,8 @@ declare_resource(:resource_type, 'resource_name', resource_attrs_block)
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
- `resource_attrs_block` is a block in which properties of the instantiated resource are declared.
For example:
@@ -55,8 +55,8 @@ delete_resource(:resource_type, 'resource_name')
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
For example:
@@ -67,7 +67,7 @@ delete_resource(:template, '/x/y.erb')
## delete_resource!
Use the `delete_resource!` method to find a resource in the resource
-collection, and then delete it. If the resource is not found, an
+collection, and then delete it. If the resource isn't found, an
exception is returned.
The syntax for the `delete_resource!` method is as follows:
@@ -78,8 +78,8 @@ delete_resource!(:resource_type, 'resource_name')
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef Infra may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef Infra may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
For example:
@@ -92,7 +92,7 @@ delete_resource!(:file, '/x/file.txt')
Use the `edit_resource` method to:
- Find a resource in the resource collection, and then edit it.
-- Define a resource block. If a resource block with the same name exists in the resource collection, it will be updated with the contents of the resource block defined by the `edit_resource` method. If a resource block does not exist in the resource collection, it will be created.
+- Define a resource block. If a resource block with the same name exists in the resource collection, it will be updated with the contents of the resource block defined by the `edit_resource` method. If a resource block doesn't exist in the resource collection, it will be created.
The syntax for the `edit_resource` method is as follows:
@@ -102,8 +102,8 @@ edit_resource(:resource_type, 'resource_name', resource_attrs_block)
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
- `resource_attrs_block` is a block in which properties of the instantiated resource are declared.
For example:
@@ -132,7 +132,7 @@ Use the `edit_resource!` method to:
- Find a resource in the resource collection, and then edit it.
- Define a resource block. If a resource with the same name exists in the resource collection, its properties will be updated with the contents of the resource block defined by the `edit_resource` method.
-In both cases, if the resource is not found, an exception is returned.
+In both cases, if the resource isn't found, an exception is returned.
The syntax for the `edit_resource!` method is as follows:
@@ -142,8 +142,8 @@ edit_resource!(:resource_type, 'resource_name')
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
- `resource_attrs_block` is a block in which properties of the instantiated resource are declared.
For example:
@@ -157,7 +157,7 @@ edit_resource!(:file, '/x/y.rst')
Use the `find_resource` method to:
- Find a resource in the resource collection.
-- Define a resource block. If a resource block with the same name exists in the resource collection, it will be returned. If a resource block does not exist in the resource collection, it will be created.
+- Define a resource block. If a resource block with the same name exists in the resource collection, it will be returned. If a resource block doesn't exist in the resource collection, it will be created.
The syntax for the `find_resource` method is as follows:
@@ -167,8 +167,8 @@ find_resource(:resource_type, 'resource_name')
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
For example:
@@ -189,7 +189,7 @@ end
## find_resource!
-Use the `find_resource!` method to find a resource in the resource collection. If the resource is not found, an exception is returned.
+Use the `find_resource!` method to find a resource in the resource collection. If the resource isn't found, an exception is returned.
The syntax for the `find_resource!` method is as follows:
@@ -199,8 +199,8 @@ find_resource!(:resource_type, 'resource_name')
where:
-- `:resource_type` is the resource type, such as `:file` (for the **file** resource), `:template` (for the **template** resource), and so on. Any resource available to Chef may be declared.
-- `resource_name` the property that is the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
+- `:resource_type` is the resource type, such as `:file` (for the **file** resource) or `:template` (for the **template** resource). Any resource available to Chef may be declared.
+- `resource_name` the property that's the default name of the resource, typically the string that appears in the `resource 'name' do` block of a resource (but not always); see the Syntax section for the resource to be declared to verify the default name property.
For example:
diff --git a/content/infra_language/reading_data_bags.md b/content/infra_language/reading_data_bags.md
index c74bbcbf31..524d98c3f6 100644
--- a/content/infra_language/reading_data_bags.md
+++ b/content/infra_language/reading_data_bags.md
@@ -43,7 +43,7 @@ The syntax for the `data_bag_item` method is as follows:
data_bag_item(bag_name, item, secret)
```
-where `secret` is the secret used to load an encrypted data bag. If `secret` is not specified, Chef Infra Client looks for a secret at the path specified by the `encrypted_data_bag_secret` setting in the `client.rb` file.
+where `secret` is the secret used to load an encrypted data bag. If `secret` isn't specified, Chef Infra Client looks for a secret at the path specified by the `encrypted_data_bag_secret` setting in the `client.rb` file.
### Examples
diff --git a/content/infra_language/shelling_out.md b/content/infra_language/shelling_out.md
index 247c1a2f06..9f8154b8b6 100644
--- a/content/infra_language/shelling_out.md
+++ b/content/infra_language/shelling_out.md
@@ -23,7 +23,7 @@ The syntax for the `shell_out` method is as follows:
shell_out(command_args)
```
-where `command_args` is the command that is run against the node.
+where `command_args` is the command that's run against the node.
## shell_out!
@@ -35,4 +35,4 @@ The syntax for the `shell_out!` method is as follows:
shell_out!(command_args)
```
-where `command_args` is the command that is run against the node. This method will return `true` or `false`.
+where `command_args` is the command that's run against the node. This method will return `true` or `false`.
diff --git a/content/install_bootstrap.md b/content/install_bootstrap.md
index 63a6351635..aabdae64be 100644
--- a/content/install_bootstrap.md
+++ b/content/install_bootstrap.md
@@ -1,5 +1,5 @@
+++
-title = "Bootstrap a Node"
+title = "Bootstrap a node"
draft = false
gh_repo = "chef-web-docs"
aliases = ["/install_bootstrap.html"]
@@ -23,21 +23,26 @@ product = ["client", "workstation"]
### Run the bootstrap command
-The `knife bootstrap` subcommand is used to run a bootstrap operation that installs Chef Infra Client on the target node. The following steps describe how to bootstrap a node using knife.
+The `knife bootstrap` command runs a bootstrap operation that installs Chef Infra Client on a target node. The following steps describe how to bootstrap a node using knife.
1. Identify the FQDN or IP address of the target node. The `knife bootstrap` command requires the FQDN or the IP address for the node to complete the bootstrap operation.
-2. Once the workstation machine is configured, it can be used to install Chef Infra Client on one (or more) nodes across the organization using a knife bootstrap operation. The `knife bootstrap` command is used to SSH into the target machine, and then do what is needed to allow Chef Infra Client to run on the node. It will install the Chef Infra Client executable (if necessary), generate keys, and register the node with the Chef Infra Server. The bootstrap operation requires the IP address or FQDN of the target system, the SSH credentials (username, password or identity file) for an account that has root access to the node, and (if the operating system is not Ubuntu, which is the default distribution used by `knife bootstrap`) the operating system running on the target system.
+2. Once the workstation machine is configured, it can be used to install Chef Infra Client on one (or more) nodes across the organization using a knife bootstrap operation. The `knife bootstrap` command is used to SSH into the target machine, and then do what's needed to allow Chef Infra Client to run on the node. It will install the Chef Infra Client executable (if necessary), generate keys, and register the node with the Chef Infra Server. The bootstrap operation requires the IP address or FQDN of the target system, the SSH credentials (username, password or identity file) for an account that has root access to the node, and (if the operating system isn't Ubuntu, which is the default distribution used by `knife bootstrap`) the operating system running on the target system.
In a command window, enter the following:
```bash
- knife bootstrap 172.16.1.233 -U USERNAME --sudo
+ knife bootstrap -U --sudo
```
- where `172.16.1.233` is the IP address or the FQDN for the node, and `USERNAME` is the username you want to use to connect, and `--sudo` specifies to elevate privileges using the sudo command on UNIX-based systems.
+ Replace:
- Then while the bootstrap operation is running, the command window will show something similar to the following:
+ - `` the IP address or the FQDN of the node
+ - `` with the username used to connect to the node
+
+ The `--sudo` option elevates privileges using the sudo command on UNIX-based systems.
+
+ While the bootstrap operation is running, the command window returns something similar to the following:
```bash
Enter password for ubuntu@172.16.1.233:
@@ -123,7 +128,7 @@ The `knife bootstrap` subcommand is used to run a bootstrap operation that insta
client2
```
-## Validatorless and Legacy Validator Bootstraps
+## Validatorless and legacy validator bootstraps
We recommended using "validatorless bootstrapping" to authenticate new nodes with the Chef Infra Server.
@@ -131,8 +136,8 @@ The legacy Chef Infra validator-based node bootstrapping process depended on usi
Shortcomings of the legacy validator process are:
-* All users share the same key for bootstrapping new systems
-* Key sharing makes key rotation difficult, if it is compromised or if an employee leaves the organization.
+- All users share the same key for bootstrapping new systems
+- Key sharing makes key rotation difficult, if it's compromised or if an employee leaves the organization.
The "validatorless bootstrap" generates a key for each node, which is then transferred to the new node and used to authenticate with the Chef Infra Server instead of relying on a shared "validator" key.
@@ -152,7 +157,7 @@ Use the following options with a validatorless bootstrap to specify items that a
`--bootstrap-vault-json VAULT_JSON`
-: A JSON string that contains a list of vaults and items to be updated. --bootstrap-vault-json '{ "vault1": \["item1", "item2"\], "vault2": "item2" }'
+: A JSON string that contains a list of vaults and items to be updated. `--bootstrap-vault-json '{ "vault1": \["item1", "item2"\], "vault2": "item2" }'`
## Examples
@@ -175,7 +180,7 @@ cat sea-power-content.json
knife vault create sea power -M client -A sean_horn,angle -J sea-power-content.json
```
-No clients, because the `-S` option was not specified while creating the vault.
+No clients, because the `-S` option wasn't specified while creating the vault.
At this time, only the users `sean_horn` and `angle` are authorized to read and manage the vault.
@@ -190,7 +195,7 @@ search_query:
some: content for them
```
-It is definitely an encrypted databag, see?
+It's definitely an encrypted databag, see?
```bash
knife data_bag show sea power
@@ -344,27 +349,28 @@ search_query:
some: content for them
```
-## Unattended Installs
+## Unattended installs
-Chef Infra Client can be installed using an unattended bootstrap. This allows Chef Infra Client to be installed from itself, without requiring SSH. For example, machines are often created using environments like AWS Auto Scaling, AWS CloudFormation, Rackspace Auto Scale, and PXE. In this scenario, using tooling for attended, single-machine installs like `knife bootstrap` or `knife CLOUD_PLUGIN create` is not practical because the machines are created automatically and someone cannot always be on-hand to initiate the bootstrap process.
+Chef Infra Client can be installed using an unattended bootstrap. This allows Chef Infra Client to be installed from itself, without requiring SSH. For example, machines are often created using environments like AWS Auto Scaling, AWS CloudFormation, Rackspace Auto Scale, and PXE. In this scenario, using tooling for attended, single-machine installs like `knife bootstrap` or `knife CLOUD_PLUGIN create` isn't practical because the machines are created automatically and someone can't always be on-hand to initiate the bootstrap process.
When Chef Infra Client is installed using an unattended bootstrap, remember that Chef Infra Client:
-* Must be able to authenticate to the Chef Infra Server
-* Must be able to configure a run-list
-* May require custom attributes, depending on the cookbooks that are being used
-* Must be able to access the chef-validator.pem so that it may create a new identity on the Chef Infra Server
-* Must have a unique node name; Chef Infra Client will use the FQDN for the host system by default
+- Must be able to authenticate to the Chef Infra Server.
+- Must be able to configure a run-list.
+- May require custom attributes, depending on the cookbooks that are being used.
+- Must be able to access the `chef-validator.pem` file so that it may create a new identity on the Chef Infra Server.
+- Must have a unique node name; Chef Infra Client will use the FQDN for the host system by default.
When Chef Infra Client is installed using an unattended bootstrap, it may be built into an image that starts Chef Infra Client on boot, or installed using User Data or some other kind of post-deployment script. The type of image or User Data used depends on the platform on which the unattended bootstrap will take place.
-### Bootstrapping with User Data
+### Bootstrapping with user data
-The method used to inject a user data script into a server will vary depending on the infrastructure platform being used. For example, on AWS you can pass this data in as a text file using the command line tool.
+The method used to inject a user data script into a server varies depending on the infrastructure platform being used.
+For example, on AWS you can pass this data in as a text file using the command line.
The following user data examples demonstrate the process of bootstrapping Windows and Linux nodes.
-#### PowerShell User Data
+#### PowerShell user data
```powershell
## Set host file so the instance knows where to find chef-server
@@ -372,8 +378,8 @@ $hosts = "1.2.3.4 hello.example.com"
$file = "C:\Windows\System32\drivers\etc\hosts"
$hosts | Add-Content $file
-## Download the Chef Infra Client
-$clientURL = "https://packages.chef.io/files/stable/chef/12.19.36/windows/2012/chef-client-.msi"
+## Download Chef Infra Client
+$clientURL = "https://chefdownload-commercial.chef.io/stable/client/download?p=windows>&pv=&m=&v=&license_id="
$clientDestination = "C:\chef-client.msi"
Invoke-WebRequest $clientURL -OutFile $clientDestination
@@ -402,7 +408,7 @@ Set-Content -Path c:\chef\client.rb -Value $clientrb
C:\opscode\chef\bin\chef-client.bat -j C:\chef\first-boot.json
```
-#### Bash User Data
+#### Bash user data
```bash
#!/bin/bash -xev
@@ -422,7 +428,7 @@ EOF
cd /etc/chef/
# Install chef
-curl -L https://omnitruck.chef.io/install.sh | bash || error_exit 'could not install chef'
+curl -L https://omnitruck.chef.io/install.sh | bash || error_exit "couldn't install chef"
# Create first-boot.json
cat > "/etc/chef/first-boot.json" << EOF
@@ -447,7 +453,7 @@ EOF
chef-client -j /etc/chef/first-boot.json
```
-It is important that settings in the [client.rb file](/config_rb_client/)---`chef_server_url`, `http_proxy`, and so on are used---to ensure that configuration details are built into the unattended bootstrap process.
+It's important that settings in the [client.rb file](/config_rb_client/)---for example `chef_server_url` and `http_proxy`---are used to ensure that configuration details are built into the unattended bootstrap process.
##### Setting the initial run-list
diff --git a/content/install_chef_air_gap.md b/content/install_chef_air_gap.md
index 473f4f37b8..9352424f17 100644
--- a/content/install_chef_air_gap.md
+++ b/content/install_chef_air_gap.md
@@ -22,15 +22,16 @@ network.
Since a variety of different practices are used to create an air-gapped network, this guide focuses solely on the implementation of Chef software - as such, it makes the following assumptions:
-* You have a way to get packages to your air-gapped machines
-* Machines on your air-gapped network are able to resolve each other using DNS
-* A server's Fully Qualified Domain Name (FQDN) is the name that will be used by other servers to access it
-* You have a private Ruby gem mirror to supply gems as needed
-* You have an artifact store for file downloads. At a minimum, it should have the following packages available:
- * Chef Workstation
- * Chef Infra Client
- * Chef Supermarket
- * An [install script](/install_chef_air_gap/#create-an-install-script) for Chef Infra Client
+- You have a way to get packages to your air-gapped machines
+- Machines on your air-gapped network are able to resolve each other using DNS
+- A server's Fully Qualified Domain Name (FQDN) is the name that will be used by other servers to access it
+- You have a private Ruby gem mirror to supply gems as needed
+- You have an artifact store for file downloads. At a minimum, it should have the following packages available:
+
+ - Chef Workstation
+ - Chef Infra Client
+ - Chef Supermarket
+ - An [install script](/install_chef_air_gap/#create-an-install-script) for Chef Infra Client
### Required cookbooks
@@ -39,18 +40,18 @@ This guide will link to the required cookbooks for each piece of software in tha
For Chef Supermarket:
-* [supermarket-omnibus-cookbook](https://supermarket.chef.io/cookbooks/supermarket-omnibus-cookbook)
-* [chef-ingredient](https://supermarket.chef.io/cookbooks/chef-ingredient)
-* [hostsfile](https://supermarket.chef.io/cookbooks/hostsfile)
+- [supermarket-omnibus-cookbook](https://supermarket.chef.io/cookbooks/supermarket-omnibus-cookbook)
+- [chef-ingredient](https://supermarket.chef.io/cookbooks/chef-ingredient)
+- [hostsfile](https://supermarket.chef.io/cookbooks/hostsfile)
-### Required Gems
+### Required gems
The following Ruby gems are required to install private Supermarket using the supermarket-omnibus-cookbook:
-* mixlib-install
-* mixlib-shellout
-* mixlib-versioning
-* artifactory
+- mixlib-install
+- mixlib-shellout
+- mixlib-versioning
+- artifactory
These should be accessible from your Gem mirror.
@@ -72,16 +73,16 @@ The install script should be accessible from your artifact store.
In this section you'll install the Chef Infra Server, and create your
organization and user. Note that to configure Supermarket later
-in this guide, you will need a user that is a member of the `admins`
+in this guide, you will need a user that's a member of the `admins`
group.
1. Download the package from [Chef Downloads](https://www.chef.io/downloads).
-2. Upload the package to the machine that will run the Chef Infra Server, and then record its location on the file system. The rest of these steps assume this location is in the `/tmp` directory.
+1. Upload the package to the machine that will run the Chef Infra Server, and then record its location on the file system. The rest of these steps assume this location is in the `/tmp` directory.
-3. {{< readfile file="content/server/reusable/md/install_chef_server_install_package.md" >}}
+1. {{< readfile file="content/server/reusable/md/install_chef_server_install_package.md" >}}
-4. Run the following to start all of the services:
+1. Run the following to start all of the services:
```bash
sudo chef-server-ctl reconfigure
@@ -91,9 +92,9 @@ group.
that work together to create a functioning system, this step may
take a few minutes to complete.
-5. {{< readfile file="content/server/reusable/md/ctl_chef_server_user_create_admin.md">}}
+1. {{< readfile file="content/server/reusable/md/ctl_chef_server_user_create_admin.md">}}
-6. {{< readfile file="content/server/reusable/md/ctl_chef_server_org_create_summary.md">}}
+1. {{< readfile file="content/server/reusable/md/ctl_chef_server_org_create_summary.md">}}
## Chef Workstation
@@ -107,19 +108,19 @@ group.
dpkg -i chef-workstation_0.14.16-1_amd64.deb
```
-2. Use the `chef generate repo` command to generate your Chef repo:
+1. Use the `chef generate repo` command to generate your Chef repo:
```bash
chef generate repo chef-repo
```
-3. Within your Chef repo, create a `.chef` directory:
+1. Within your Chef repo, create a `.chef` directory:
```bash
mkdir /chef-repo/.chef
```
-4. Copy the `USER.pem` and `ORGANIZATION.pem` files from the server,
+1. Copy the `USER.pem` and `ORGANIZATION.pem` files from the server,
and move them into the `.chef` directory.
```bash
@@ -130,7 +131,7 @@ group.
By default, `knife bootstrap` uses the `chef-full` template to bootstrap
a node. This template contains a number of useful features, but it also
-attempts to pull an installation script from `packages.chef.io`. In
+attempts to pull an installation script from `https://omnitruck.chef.io`. In
this section, you'll copy the contents of the `chef-full` template to a
custom template, and then modify the package and Ruby gem sources.
@@ -141,15 +142,14 @@ custom template, and then modify the package and Ruby gem sources.
mkdir bootstrap
```
-2. Move to the `bootstrap` directory and create a blank template file;
+1. Move to the `bootstrap` directory and create a blank template file;
this example will use `airgap.erb` for the template name:
```bash
touch airgap.erb
```
-3. Still in the `bootstrap` directory, issue the following command to
- copy the `chef-full` configuration to your new template:
+1. Still in the `bootstrap` directory, issue the following command to copy the `chef-full` configuration to your new template:
```bash
find /opt/chef-workstation/embedded/lib/ruby -type f -name chef-full.erb -exec cat {} \; > airgap.erb
@@ -161,14 +161,13 @@ custom template, and then modify the package and Ruby gem sources.
template file name, be sure to replace `airgap.erb` with the
template file you created during the last step.
-4. Update `airgap.erb` to replace `omnitruck.chef.io` with the URL of
- `install.sh` on your artifact store:
+1. Update `airgap.erb` to replace `omnitruck.chef.io` with the URL of `install.sh` on your artifact store:
```ruby
install_sh="<%= knife_config[:bootstrap_url] ? knife_config[:bootstrap_url] : "http://packages.example.com/install.sh" %>"
```
-5. Still in your text editor, locate the following line near the bottom
+1. Still in your text editor, locate the following line near the bottom
of your `airgap.erb` file:
```ruby
@@ -187,7 +186,7 @@ custom template, and then modify the package and Ruby gem sources.
```
This appends the appropriate `rubygems_url` setting to the
- `/etc/chef/client.rb` file that is created during bootstrap, which
+ `/etc/chef/client.rb` file that's created during bootstrap, which
ensures that your nodes use your internal gem mirror.
### Configure knife
@@ -233,27 +232,27 @@ In this section, you will use a wrapper around the
to install private Supermarket. The Supermarket cookbook depends upon
the following cookbooks:
-* [chef-ingredient](https://supermarket.chef.io/cookbooks/chef-ingredient)
-* [hostsfile](https://supermarket.chef.io/cookbooks/hostsfile)
+- [chef-ingredient](https://supermarket.chef.io/cookbooks/chef-ingredient)
+- [hostsfile](https://supermarket.chef.io/cookbooks/hostsfile)
The following Gems must be accessible using your Gem mirror:
-* mixlib-install
-* mixlib-shellout
-* mixlib-versioning
-* artifactory
+- mixlib-install
+- mixlib-shellout
+- mixlib-versioning
+- artifactory
Your `cookbooks` directory must have all three of these cookbooks
installed before you will be able to use the Supermarket cookbook
wrapper. In addition the necessary cookbooks, a private Chef Supermarket
has the following requirements:
-* An operational Chef Infra Server to act as the OAuth 2.0 provider
-* A user account on the Chef Infra Server with `admins` privileges
-* A key for the user account on the Chef server
-* An x86_64 Ubuntu, RHEL, or Amazon Linux host with at least 1 GB memory
-* System clocks synchronized on the Chef Infra Server and Supermarket hosts
-* Sufficient disk space to meet project cookbook storage capacity or credentials to store cookbooks in an Amazon Simple Storage Service (S3) bucket
+- An operational Chef Infra Server to act as the OAuth 2.0 provider
+- A user account on the Chef Infra Server with `admins` privileges
+- A key for the user account on the Chef server
+- An x86_64 Ubuntu, RHEL, or Amazon Linux host with at least 1 GB memory
+- System clocks synchronized on the Chef Infra Server and Supermarket hosts
+- Sufficient disk space to meet project cookbook storage capacity or credentials to store cookbooks in an Amazon Simple Storage Service (S3) bucket
### Configure credentials
@@ -266,17 +265,17 @@ Supermarket.
admin-level user. If running a multi-node Chef Infra Server cluster,
log on to the node acting as the primary node in the cluster.
-2. Update the `/etc/opscode/chef-server.rb` configuration file.
+1. Update the `/etc/opscode/chef-server.rb` configuration file.
{{< readfile file="content/server/reusable/md/config_ocid_application_hash_supermarket.md" >}}
-3. Reconfigure the Chef Infra Server.
+1. Reconfigure the Chef Infra Server.
```bash
sudo chef-server-ctl reconfigure
```
-4. Retrieve Supermarket's OAuth 2.0 client credentials:
+1. Retrieve Supermarket's OAuth 2.0 client credentials:
Depending on your Chef Infra Server version and configuration (see
[chef-server.rb](/server/config_rb_server_optional_settings/#config-rb-server-insecure-addon-compat)),
@@ -301,13 +300,13 @@ Supermarket.
chef generate cookbook my_supermarket_wrapper
```
-2. Change directories into that cookbook:
+1. Change directories into that cookbook:
```bash
cd my_supermarket_wrapper
```
-3. Defines the wrapper cookbook's dependency on the
+1. Defines the wrapper cookbook's dependency on the
`supermarket-omnibus-cookbook` cookbook. Open the `metadata.rb` file
of the newly-created cookbook, and then add the following line:
@@ -315,9 +314,9 @@ Supermarket.
depends 'supermarket-omnibus-cookbook'
```
-4. Save and close the `metadata.rb` file.
+1. Save and close the `metadata.rb` file.
-5. Open the `/recipes/default.rb` recipe located within the
+1. Open the `/recipes/default.rb` recipe located within the
newly-generated cookbook and add the following content:
```ruby
@@ -337,12 +336,12 @@ and then reference them from the recipe. For example, the data bag could
be named `apps` and then a data bag item within the data bag could be
named `supermarket`. The following attributes are required:
-* `chef_server_url`: the url for your chef server.
-* `chef_oauth2_app_id`: the Chef Identity uid from
+- `chef_server_url`: the URL of your Chef Infra Server.
+- `chef_oauth2_app_id`: the Chef Identity UID from
`/etc/opscode/oc-id-applications/supermarket.json`
-* `chef_oauth2_secret`: The Chef Identity secret from
+- `chef_oauth2_secret`: The Chef Identity secret from
`/etc/opscode/oc-id-applications/supermarket.json`
-* `package_url`: The location of the Supermarket package on your
+- `package_url`: The location of the Supermarket package on your
artifact store
To define these attributes, do the following:
@@ -356,7 +355,7 @@ To define these attributes, do the following:
app = data_bag_item('apps', 'supermarket')
```
-2. Set the attributes from the data bag:
+1. Set the attributes from the data bag:
```ruby
node.override['supermarket_omnibus']['chef_server_url'] = app['chef_server_url']
@@ -391,9 +390,9 @@ To define these attributes, do the following:
include_recipe 'supermarket-omnibus-cookbook'
```
-3. Save and close the `recipes/default.rb` file.
+1. Save and close the `recipes/default.rb` file.
-4. Upload all of your cookbooks to the Chef Infra Server:
+1. Upload all of your cookbooks to the Chef Infra Server:
```ruby
knife cookbook upload -a
@@ -411,10 +410,10 @@ knife bootstrap ip_address -N supermarket-node -x ubuntu --sudo
where:
-* `-N` defines the name of the Chef Supermarket node:
+- `-N` defines the name of the Chef Supermarket node:
`supermarket-node`
-* `-x` defines the (ssh) user name: `ubuntu`
-* `--sudo` ensures that sudo is used while running commands on the
+- `-x` defines the (ssh) user name: `ubuntu`
+- `--sudo` ensures that sudo is used while running commands on the
node during the bootstrap operation
When the bootstrap operation is finished, do the following:
@@ -429,14 +428,14 @@ When the bootstrap operation is finished, do the following:
where `supermarket-node` is the name of the node that was just
bootstrapped.
-2. Start Chef Infra Client on the newly-bootstrapped Chef Supermarket
+1. Start Chef Infra Client on the newly-bootstrapped Chef Supermarket
node. For example, using SSH:
```bash
ssh ubuntu@your-supermarket-node-public-dns
```
-3. After accessing the Chef Supermarket node, run Chef Infra Client:
+1. After accessing the Chef Supermarket node, run Chef Infra Client:
```bash
sudo chef-client
@@ -446,18 +445,18 @@ When the bootstrap operation is finished, do the following:
To reach the newly spun up private Chef Supermarket, the hostname must
be resolvable from a workstation. For production use, the hostname
-should have a DNS entry in an appropriate domain that is trusted by each
+should have a DNS entry in an appropriate domain that's trusted by each
user's workstation.
1. Visit the Chef Supermarket hostname in the browser. A private Chef
Supermarket will generate and use a self-signed certificate, if a
- certificate is not supplied as part of the installation process (using
+ certificate isn't supplied as part of the installation process (using
the wrapper cookbook).
-2. If an SSL notice is shown due to your self-signed certificate while
+1. If an SSL notice is shown due to your self-signed certificate while
connecting to Chef Supermarket using a web browser, accept the SSL
certificate. A trusted SSL certificate should be used for private
- Chef Supermarket that is used in production.
-3. After opening Chef Supermarket in a web browser, click the **Create
+ Chef Supermarket that's used in production.
+1. After opening Chef Supermarket in a web browser, click the **Create
Account** link. A prompt to log in to the Chef Infra Server is
shown. Authorize the Chef Supermarket to use the Chef Infra Server
account for authentication.
@@ -467,7 +466,7 @@ user's workstation.
The redirect URL specified for Chef Identity **MUST** match the FQDN
hostname of the Chef Supermarket server. The URI must also be correct:
`/auth/chef_oauth2/callback`. Otherwise, an error message similar to
-`The redirect uri included is not valid.` will be shown.
+`The redirect uri included isn't valid.` will be shown.
{{< /note >}}
diff --git a/content/licensing/terms.md b/content/licensing/terms.md
index 35da094a46..1dbb9452ba 100644
--- a/content/licensing/terms.md
+++ b/content/licensing/terms.md
@@ -27,7 +27,7 @@ Licensed Unit
: "License Unit" types/metrics include node, entitled content, service instance, target and/or endpoint.
Measurement of License Units/License Consumption Data
-: Measurement of usage of a license unit. It's a numerical value based on the bundle\SKU or add-on(s) customer has purchased.
+: Measurement of usage of a license unit. It's a numerical value based on the bundle\SKU or add-ons customer has purchased.
Free-tier Users
: Users using a Free License of Chef (User will only get the executable but restricted in some way), not the code base.
diff --git a/content/lwrp_to_custom_resources.md b/content/lwrp_to_custom_resources.md
index 7c15ae6d66..526b1e6765 100644
--- a/content/lwrp_to_custom_resources.md
+++ b/content/lwrp_to_custom_resources.md
@@ -14,7 +14,7 @@ product = ["client", "workstation"]
## Overview
-It is no longer recommended to write resources in the __Light Weight Resource Provider (LWRP)__ format.
+It's no longer recommended to write resources in the __Light Weight Resource Provider (LWRP)__ format.
This guide describes how to migrate from an existing LWRP to a Custom Resource.
@@ -39,7 +39,7 @@ These files are merged into one, and moved into the resources directory.
## Drop LWRP classes
-LWRPs used classes to separate Provider and Resource behaviors, but Custom Resources do not need this distinction. This means that we remove the class definitions in their entirety, as shown in the following example:
+LWRPs used classes to separate Provider and Resource behaviors, but Custom Resources don't need this distinction. This means that we remove the class definitions in their entirety, as shown in the following example:
```ruby
#rvm/libraries/resource_rvm_ruby.rb
@@ -98,7 +98,7 @@ end
## Remove Attributes
-It is best practice to use properties to change the behavior of resources.
+It's best practice to use properties to change the behavior of resources.
In the previous example example we used an attribute to change the `installer_url`.
diff --git a/content/manage.md b/content/manage.md
index 63780700aa..61b6bbce59 100644
--- a/content/manage.md
+++ b/content/manage.md
@@ -22,7 +22,7 @@ product = []
{{< note >}}
-Chef Automate 2 does not deploy Chef Manage alongside Chef Infra Server.
+Chef Automate 2 doesn't deploy Chef Manage alongside Chef Infra Server.
{{< /note >}}
diff --git a/content/nodes.md b/content/nodes.md
index a216a505ad..78445a50e1 100644
--- a/content/nodes.md
+++ b/content/nodes.md
@@ -69,11 +69,11 @@ across the organization are unique.
For Chef Infra Client, two important aspects of nodes are groups of
attributes and run-lists. An attribute is a specific piece of data about
-the node, such as a network interface, a file system, the number of
-clients a service running on a node is capable of accepting, and so on.
+the node, such as a network interface, a file system, or the number of
+clients a service running on a node is capable of accepting.
A run-list is an ordered list of recipes and/or roles that are run in an
exact order. The node object consists of the run-list and node
-attributes, which is a JSON file that is stored on the Chef Infra
+attributes, which is a JSON file that's stored on the Chef Infra
Server. Chef Infra Client gets a copy of the node object from the Chef
Infra Server during each Chef Infra Client run and places an updated
copy on the Chef Infra Server at the end of each Chef Infra Client run.
@@ -83,8 +83,8 @@ copy on the Chef Infra Server at the end of each Chef Infra Client run.
### Attributes
An attribute is a specific detail about a node, such as an IP address, a
-host name, a list of loaded kernel modules, the version(s) of available
-programming languages that are available, and so on. An attribute may be
+host name, a list of loaded kernel modules, the versions of available
+programming languages that are available. An attribute may be
unique to a specific node or it can be identical across every node in
the organization. Attributes are most commonly set from a cookbook, by
using knife, or are retrieved by Ohai from each node before every Chef
@@ -111,7 +111,7 @@ attributes from the attribute file, and the attributes set by the role
will take precedence over the attributes specified in the cookbook's
attribute files.
-See [Attributes](/attributes) for detailed information on the different types of node attributes and how they are used to set policy on nodes.
+See [Attributes](/attributes) for detailed information on the different types of node attributes and how they're used to set policy on nodes.
### Run-lists
@@ -128,4 +128,4 @@ You can manage nodes directly using Knife, Chef Automate, or by using command-li
- [Knife](/workstation/knife/) can be used to create, edit, view, list, tag, and delete nodes.
- Knife plug-ins can be used to create, edit, and manage nodes that are located on cloud providers.
- Chef Infra Client can be used to manage node data using the command line and JSON files. Each JSON file contains a hash, the elements of which are added as node attributes. In addition, the `run_list` setting allows roles and/or recipes to be added to the node.
-- The command line can also be used to edit JSON files and files that are related to third-party services, such as Amazon EC2, where the JSON files can contain metadata fore each instance that is stored in a file on-disk and then read by Chef Infra Client as required.
+- The command line can also be used to edit JSON files and files that are related to third-party services, such as Amazon EC2, where the JSON files can contain metadata fore each instance that's stored in a file on-disk and then read by Chef Infra Client as required.
diff --git a/content/ohai.md b/content/ohai.md
index 82840b2078..a19f530b81 100644
--- a/content/ohai.md
+++ b/content/ohai.md
@@ -257,7 +257,7 @@ Custom Ohai plugins can be written to collect additional information from system
## Hints
-Ohai hints are used to tell Ohai something about the system that it is running on that it would not be able to discover itself. An Ohai hint exists if a JSON file exists in the hint directory with the same name as the hint. For example, calling `hint?('antarctica')` in an Ohai plugin would return an empty hash if the file `antarctica.json` existed in the hints directory, and return nil if the file does not exist.
+Ohai hints are used to tell Ohai something about the system that it's running on that it would not be able to discover itself. An Ohai hint exists if a JSON file exists in the hint directory with the same name as the hint. For example, calling `hint?('antarctica')` in an Ohai plugin would return an empty hash if the file `antarctica.json` existed in the hints directory, and return nil if the file doesn't exist.
If the hint file contains JSON content, it will be returned as a hash from the call to `hint?`.
diff --git a/content/ohai_custom.md b/content/ohai_custom.md
index a1a643d5a7..3c76c6a75c 100644
--- a/content/ohai_custom.md
+++ b/content/ohai_custom.md
@@ -62,12 +62,12 @@ end
where
- Required. `(:Name)` is used to identify the plugin; when two plugins have the same `(:Name)`, those plugins are joined together and run as if they were a single plugin. This value must be a valid Ruby class name, starting with a capital letter and containing only alphanumeric characters
-- Required. `provides` is a comma-separated list of one (or more) attributes that are defined by this plugin. This attribute will become an automatic attribute (`node['attribute']`) after it is collected by Ohai at the start of a Chef Infra Client run. An attribute can also be defined using an `attribute/subattribute` pattern
+- Required. `provides` is a comma-separated list of one (or more) attributes that are defined by this plugin. This attribute will become an automatic attribute (`node['attribute']`) after it's collected by Ohai at the start of a Chef Infra Client run. An attribute can also be defined using an `attribute/subattribute` pattern
- `depends` is a comma-separated list of one (or more) attributes that are collected by another plugin; as long as the value is collected by another Ohai plugin, it can be used by any plugin
- `shared_method` defines code that can be shared among one (or more) `collect_data` blocks; for example, instead of defining a mash for each `collect_data` block, the code can be defined as a shared method, and then called from any `collect_data` block
-- `collect_data` is a block of Ruby code that is called by Ohai when it runs; one (or more) `collect_data` blocks can be defined in a plugin, but only a single `collect_data` block is ever run.
-- `collect_data(:default)` is the code block that runs when a node's platform is not defined by a platform-specific `collect_data` block
-- `collect_data(:platform)` is a platform-specific code block that is run when a match exists between the node's platform and this `collect_data` block; only one `collect_data` block may exist for each platform; possible values: `:aix`, `:darwin`, `:freebsd`, `:linux`, `:openbsd`, `:netbsd`, `:solaris2`, `:windows`, or any other value from `RbConfig::CONFIG['host_os']`
+- `collect_data` is a block of Ruby code that's called by Ohai when it runs; one (or more) `collect_data` blocks can be defined in a plugin, but only a single `collect_data` block is ever run.
+- `collect_data(:default)` is the code block that runs when a node's platform isn't defined by a platform-specific `collect_data` block
+- `collect_data(:platform)` is a platform-specific code block that's run when a match exists between the node's platform and this `collect_data` block; only one `collect_data` block may exist for each platform; possible values: `:aix`, `:darwin`, `:freebsd`, `:linux`, `:openbsd`, `:netbsd`, `:solaris2`, `:windows`, or any other value from `RbConfig::CONFIG['host_os']`
- `my_data` is string (`a string value`) or an empty mash (`{ :setting_a => 'value_a', :setting_b => 'value_b' }`). This is used to define the data that should be collected by the plugin
For example, the following plugin looks up data on virtual machines hosted in Amazon EC2, Google Compute Engine, Rackspace, Eucalyptus, Linode, OpenStack, and Microsoft Azure:
@@ -133,16 +133,16 @@ To see the rest of the code in this plugin, go to: e
- Ohai::Log.debug('ip_scopes: cannot load gem, plugin disabled: #{e}')
+ Ohai::Log.debug('ip_scopes: can't load gem, plugin disabled: #{e}')
end
```
@@ -531,7 +531,7 @@ Ohai.plugin(:Hostname) do
if info.first =~ /.+?\.(.*)/
fqdn info.first
else
- # host is not in dns. optionally use:
+ # host isn't in dns. optionally use:
# C:\WINDOWS\system32\drivers\etc\hosts
fqdn Socket.gethostbyaddr(info.last).first
end
diff --git a/content/packages.md b/content/packages.md
index bc0fd3a527..92222e8531 100644
--- a/content/packages.md
+++ b/content/packages.md
@@ -108,7 +108,7 @@ To set up a Yum package repository for Enterprise Linux platforms:
```
Note that the `yum-config-manager` command requires the `yum-utils`
- package, which is not installed on CentOS by default. You can
+ package, which isn't installed on CentOS by default. You can
install the package by running `sudo yum install yum-utils`, or you
can use the `mv` command to add the repository to the
`/etc/yum.repos.d/` directory:
diff --git a/content/platform_overview.md b/content/platform_overview.md
index 23bdd72224..08d85d3bf3 100644
--- a/content/platform_overview.md
+++ b/content/platform_overview.md
@@ -13,7 +13,7 @@ product = ["automate", "client", "server", "habitat", "inspec", "workstation"]
weight = 10
+++
-Chef is an automation company. Ever since it was founded in 2008, we have
+Chef is an automation company. Ever since it was founded in 2008, we've
been bringing together developers and system administrators with our
namesake product, Chef Infra. Over the years, what we mean by automation
has expanded. Today, Chef has a complete automation solution for both
@@ -30,7 +30,7 @@ development to production. Here's the complete Chef solution.
[Chef Workstation](/workstation/) allows you to author cookbooks and administer your
infrastructure. Chef Workstation runs on the computer you use everyday,
-whether it is Linux, macOS, or Windows.
+whether it's Linux, macOS, or Windows.
Chef Workstation ships with Cookstyle, ChefSpec, Chef InSpec, and Test
Kitchen testing tools. With them, you can make sure your Chef Infra code
@@ -71,7 +71,7 @@ upload your cookbooks.
Chef Infra is constructed so that most of the computational effort
occurs on the nodes rather than on the Chef Infra Server. A node
represents any system you manage and is typically a virtual machine,
-container instance, or physical server. Basically, it is any compute
+container instance, or physical server. Basically, it's any compute
resource in your infrastructure that's managed by Chef Infra. All nodes
have Chef Infra Client installed on them, and Chef Infra Client is
available for multiple platforms including Linux, macOS, Windows, AIX,
@@ -79,7 +79,7 @@ and Solaris.
Periodically, Chef Infra Client contacts the Chef Infra Server to
retrieve the latest cookbooks. If (and only if) the current state of the
-node does not conform to what the cookbook says it should be, Chef Infra
+node doesn't conform to what the cookbook says it should be, Chef Infra
Client executes the cookbook instructions. This iterative process
ensures that the network as a whole converges to the state envisioned by
business policy.
@@ -91,7 +91,7 @@ application automation. Application automation means that the automation
is packaged with the application and travels with it, no matter where
that application is deployed. The unit of deployment becomes the
application and its associated automation. The runtime environment,
-whether it is a container, bare metal, or PaaS does not in any way
+whether it's a container, bare metal, or PaaS doesn't in any way
define the application.
Chef Habitat is comprised of a packaging format and a supervisor. The
@@ -118,7 +118,7 @@ inspect the configuration of virtual resources by using their API.
To get a sense of how the Chef InSpec language works, here are some
examples. This Chef InSpec rule ensures that insecure services and
-protocols, such as telnet, are not used.
+protocols, such as telnet, aren't used.
```ruby
describe package('telnetd') do
diff --git a/content/platforms.md b/content/platforms.md
index ef801aebd9..6848763ff8 100644
--- a/content/platforms.md
+++ b/content/platforms.md
@@ -95,16 +95,16 @@ The following table lists the commercially supported platforms and versions for
| AIX | `powerpc` | `7.1` (TL5 SP2 or higher, recommended), `7.2`, `7.3` |
| Amazon Linux | `x86_64`, `aarch64` | `2.x`, `2023` |
| CentOS | `x86_64`, `ppc64le`, `ppc64`, `aarch64` | `7.x` |
-| Debian | `x86_64`, `aarch64` | `10`, `11` |
+| Debian | `x86_64` | `10`, `11` |
| FreeBSD | `amd64` | `13.x` |
| macOS | `x86_64`, `aarch64` (M1 processors) | `12.x` |
| Oracle Enterprise Linux | `x86_64`, `aarch64` | `7.x`, `8.x` |
| Red Hat Enterprise Linux | `x86_64`, `ppc64le` (7.x only), `ppc64` (7.x only), `aarch64`, `s390x` (7.x / 8.x only) | `7.x`, `8.x`, `9.x` |
-| Rocky Linux | `x86_64`, `aarch64` | `8.x`, `9.x` |
+| Rocky Linux | `x86_64` | `8.x`, `9.x` |
| Solaris | `sparc`, `i86pc` | `11.3` (16.17.4 and later only), `11.4` |
| SUSE Linux Enterprise Server | `x86_64`, `aarch64` (15.x only), `s390x` | `12`, `15` |
-| Ubuntu (LTS releases) | `x86_64`,`aarch64` | `16.04`, `18.04`, `20.04`, `22.04` |
-| Windows | `x86`, `x64` | `2012`, `2012 R2`, `2016`, `10` (all channels except "insider" builds), `2019` (Long-term servicing channel (LTSC), both Desktop Experience and Server Core), `11`, `2022` |
+| Ubuntu (LTS releases) | `x86_64`,`aarch64` (18.x and above) | `16.04`, `18.04`, `20.04`, `22.04` |
+| Windows | `x86_64` | `2016`, `10` (all channels except "insider" builds), `2019` (Long-term servicing channel (LTSC), both Desktop Experience and Server Core), `11`, `2022` |
#### Derived platforms
diff --git a/content/plugin_community.md b/content/plugin_community.md
index d672299b79..6e16e3429d 100644
--- a/content/plugin_community.md
+++ b/content/plugin_community.md
@@ -36,7 +36,7 @@ The following Ohai plugins are available from the open source community:
| dell.rb |
-Adds some useful Dell server information to Ohai. For example: service tag, express service code, storage info, RAC info, and so on. To use this plugin, OMSA and SMBIOS applications need to be installed. |
+Adds some useful Dell server information to Ohai. For example, service tag, express service code, storage info, or RAC info. To use this plugin, OMSA and SMBIOS applications need to be installed. |
| ipmi.rb |
@@ -88,11 +88,11 @@ The following Ohai plugins are available from the open source community:
| win32_software.rb |
-Adds the ability for Ohai to use Windows Management Instrumentation (WMI) to discover useful information about software that is installed on any node that is running Windows. |
+Adds the ability for Ohai to use Windows Management Instrumentation (WMI) to discover useful information about software that's installed on any node that's running Windows. |
| win32_svc.rb |
-Adds the ability for Ohai to query using Windows Management Instrumentation (WMI) to get information about all services that are registered on a node that is running Windows. |
+Adds the ability for Ohai to query using Windows Management Instrumentation (WMI) to get information about all services that are registered on a node that's running Windows. |
diff --git a/content/policyfile.md b/content/policyfile.md
index 9765a5adde..6892a90f31 100644
--- a/content/policyfile.md
+++ b/content/policyfile.md
@@ -29,13 +29,13 @@ Policyfiles make it easier to test and promote code safely with a simpler interf
### Focused System Workflows
-The knife command line tool maps closely to the Chef Infra Server API and the objects defined by it: roles, environments, run-lists, cookbooks, data bags, nodes, and so on. Chef Infra Client assembles these pieces at run-time and configures a host to do useful work.
+The knife command line tool maps closely to the Chef Infra Server API and the objects defined by it, such as roles, environments, run-lists, cookbooks, data bags, or nodes. Chef Infra Client assembles these pieces at run-time and configures a host to do useful work.
Policyfile focuses that workflow onto the entire system, rather than the individual components. For example, Policyfile describes whole systems, whereas each individual revision of the `Policyfile.lock.json` file uploaded to the Chef Infra Server describes a part of that system, inclusive of roles, environments, cookbooks, and the other Chef Infra Server objects necessary to configure that part of the system.
### Safer Workflows
-Policyfile encourages safer workflows by making it easier to publish development versions of cookbooks to the Chef Infra Server without the risk of mutating the production versions and without requiring a complicated versioning scheme to work around cookbook mutability issues. Roles are mutable and those changes are applied only to the nodes specified by the policy. Policyfile does not require any changes to your normal workflows. Use the same repositories you are already using, the same cookbooks, and workflows. Policyfile will prevent an updated cookbook or role from being applied immediately to all machines.
+Policyfile encourages safer workflows by making it easier to publish development versions of cookbooks to the Chef Infra Server without the risk of mutating the production versions and without requiring a complicated versioning scheme to work around cookbook mutability issues. Roles are mutable and those changes are applied only to the nodes specified by the policy. Policyfile doesn't require any changes to your normal workflows. Use the same repositories you are already using, the same cookbooks, and workflows. Policyfile will prevent an updated cookbook or role from being applied immediately to all machines.
### Code Visibility
@@ -49,13 +49,13 @@ When running Chef Infra without a Policyfile, the exact set of cookbooks that ar
These conditions are re-evaluated every time Chef Infra Client runs, which can make it harder to know which cookbooks will be run by Chef Infra Client or what the effects of updating a role or uploading a new cookbook will be.
-Policyfile simplifies this behavior by computing the cookbook set on the workstation, and then producing a readable document of that solution: a `Policyfile.lock.json` file. This pre-computed file is uploaded to the Chef Infra Server, and is then used in each Chef Infra Client run that is managed by that particular policy name and policy group.
+Policyfile simplifies this behavior by computing the cookbook set on the workstation, and then producing a readable document of that solution: a `Policyfile.lock.json` file. This pre-computed file is uploaded to the Chef Infra Server, and is then used in each Chef Infra Client run that's managed by that particular policy name and policy group.
### Less Expensive Computation
When running Chef Infra without Policyfile, the Chef Infra Server loads dependency data for all known versions of all known cookbooks, and then runs an expensive computation to determine the correct set.
-Policyfile moves this computation to the workstation, where it is done less frequently.
+Policyfile moves this computation to the workstation, where it's done less frequently.
### Role and Environment Mutability
@@ -65,13 +65,13 @@ Policyfile effectively replaces roles and environments. Policyfile files are ver
### Cookbook Mutability
-When running Chef without Policyfile, existing versions of cookbooks are mutable. This is convenient for many use cases, especially if users upload in-development cookbook revisions to the Chef Infra Server. But this sometimes creates issues that are similar to role mutability by allowing those cookbook changes to be applied immediately to nodes that use that cookbook. Users account for this by rigorous testing processes to ensure that only fully integrated cookbooks are ever published. This process does enforce good development habits, but at the same time it should not be a required part of a workflow that ends with publishing an in-development cookbook to the Chef Infra Server for testing against real nodes Policyfile solves this issue by using a cookbook publishing API for the Chef Infra Server that does not provide cookbook mutability. Name collisions are prevented by storing cookbooks by name and an opaque identifier that is computed from the content of the cookbook itself.
+When running Chef without Policyfile, existing versions of cookbooks are mutable. This is convenient for many use cases, especially if users upload in-development cookbook revisions to the Chef Infra Server. But this sometimes creates issues that are similar to role mutability by allowing those cookbook changes to be applied immediately to nodes that use that cookbook. Users account for this by rigorous testing processes to ensure that only fully integrated cookbooks are ever published. This process does enforce good development habits, but at the same time it shouldn't be a required part of a workflow that ends with publishing an in-development cookbook to the Chef Infra Server for testing against real nodes. Policyfile solves this issue by using a cookbook publishing API for the Chef Infra Server that doesn't provide cookbook mutability. Name collisions are prevented by storing cookbooks by name and an opaque identifier that's computed from the content of the cookbook itself.
-For example, name/version collisions can occur when users temporarily fork an upstream cookbook. Even if the user contributes their change and the maintainer is responsive, there may be a period of time where the user needs their fork to make progress. This situation presents a versioning dilemma: if the user does not update their own version, they must overwrite the existing copy of that cookbook on the Chef Infra Server, wheres if they do update the version number it might conflict with the version number of the future release of that upstream cookbook.
+For example, name/version collisions can occur when users temporarily fork an upstream cookbook. Even if the user contributes their change and the maintainer is responsive, there may be a period of time where the user needs their fork to make progress. This situation presents a versioning dilemma: if the user doesn't update their own version, they must overwrite the existing copy of that cookbook on the Chef Infra Server, wheres if they do update the version number it might conflict with the version number of the future release of that upstream cookbook.
#### Opaque IDs
-The opaque identifier that is computed from the content of a cookbook is the only place where an opaque identifier is necessary. When working with Policyfile, be sure to:
+The opaque identifier that's computed from the content of a cookbook is the only place where an opaque identifier is necessary. When working with Policyfile, be sure to:
* Use the same names and version constraints as normal in the `Policyfile.rb` file
* Use the same references to cookbooks pulled from Chef Supermarket
@@ -84,7 +84,7 @@ The opaque identifier is mostly behind the scenes and is only visible once publi
### Environment Cookbooks
-Policyfile replaces the environment cookbook pattern that is often required by Berkshelf, along with a dependency solver and fetcher. That said, Policyfile does not replace all Berkshelf scenarios.
+Policyfile replaces the environment cookbook pattern that's often required by Berkshelf, along with a dependency solver and fetcher. That said, Policyfile doesn't replace all Berkshelf scenarios.
## Knife Commands
@@ -116,7 +116,7 @@ The following settings may be configured in the client.rb file for use with Poli
`named_run_list`
-: The run-list associated with a policy file.
+: The run-list associated with a Policyfile.
`policy_group`
@@ -142,7 +142,7 @@ A node may be bootstrapped to use Policyfile files. Use the following options as
: The name of a policy, as identified by the `name` setting in a `Policyfile.rb` file.
-For a customized bootstrap process, add `policy_name` and `policy_group` to the first-boot JSON file that is passed to Chef Infra Client.
+For a customized bootstrap process, add `policy_name` and `policy_group` to the first-boot JSON file that's passed to Chef Infra Client.
## knife search
@@ -191,7 +191,7 @@ suites:
{{< note >}}
-As `chef_zero` explicitly tests outside the context of a Chef Infra Server, the `policy_groups` concept is not applicable. The value of `policy_group` during a converge will be set to `local`.
+As `chef_zero` explicitly tests outside the context of a Chef Infra Server, the `policy_groups` concept isn't applicable. The value of `policy_group` during a converge will be set to `local`.
{{< /note >}}
diff --git a/content/proxies.md b/content/proxies.md
index a1e4c4e722..1e1389565b 100644
--- a/content/proxies.md
+++ b/content/proxies.md
@@ -15,7 +15,7 @@ aliases = ["/proxies.html"]
+++
In an environment that requires proxies to reach the Internet, many Chef
-commands will not work until they are configured correctly. To configure
+commands won't work until they're configured correctly. To configure
Chef to work in an environment that requires proxies, set the
`http_proxy`, `https_proxy`, `ftp_proxy`, and/or `no_proxy` environment
variables to specify the proxy settings using a lowercase value.
@@ -33,7 +33,7 @@ check the environment variables. Run the following:
env | grep -i http_proxy
```
-If an environment variable is set, it **MUST** be lowercase. If it is
+If an environment variable is set, it **MUST** be lowercase. If it's
not, add a lowercase version of that proxy variable to the shell (for example
`~/.bashrc`) using one (or more) the following commands.
@@ -159,7 +159,7 @@ environments that use an FTP proxy:
### No Proxy
The `no_proxy` setting is used to specify addresses for which the proxy
-should not be used. This can be a single address or a comma-separated
+shouldn't be used. This can be a single address or a comma-separated
list of addresses.
Example:
@@ -172,7 +172,7 @@ no_proxy 'test.example.com,test.example2.com,test.example3.com'
Wildcard matching may be used in the `no_proxy` list---such as
`no_proxy '*.*.example.*'`---however, many situations require hostnames
-to be specified explicitly (that is, "without wildcards").
+to be specified explicitly (that's, "without wildcards").
{{< /note >}}
diff --git a/content/recipes.md b/content/recipes.md
index 75e62283c8..fd0d838fdc 100644
--- a/content/recipes.md
+++ b/content/recipes.md
@@ -47,7 +47,7 @@ end
```
The only environment being altered is the one being passed to the child
-process that is started by the **bash** resource. This will not affect
+process that's started by the **bash** resource. This won't affect
the Chef Infra Client environment or any child processes.
## Work with Recipes
@@ -106,13 +106,13 @@ mysql_creds['pass'] # will be decrypted
### Assign Dependencies
-If a cookbook has a dependency on a recipe that is located in another
+If a cookbook has a dependency on a recipe that's located in another
cookbook, that dependency must be declared in the metadata.rb file for
that cookbook using the `depends` keyword.
{{< note >}}
-Declaring cookbook dependencies is not required with chef-solo.
+Declaring cookbook dependencies isn't required with chef-solo.
{{< /note >}}
@@ -273,7 +273,7 @@ to a run-list is similar to:
}
```
-where `::default_recipe` is implied (and does not need to be specified).
+where `::default_recipe` is implied (and doesn't need to be specified).
On a node, these recipes can be assigned to a node's run-list similar
to:
@@ -395,7 +395,7 @@ end
where `platform?('windows')` is the condition set on the `return`
keyword. When the condition is met, stop processing the recipe. This
approach is useful when there is no need to continue processing, such as
-when a package cannot be installed. In this situation, it is OK for a
+when a package can't be installed. In this situation, it's OK for a
recipe to stop processing.
#### raise Keyword
@@ -490,7 +490,7 @@ specify the message to be raised.
Use `node.run_state` to stash transient data during a Chef Infra Client
run. This data may be passed between resources, and then evaluated
-during the execution phase. `run_state` is an empty Hash that is always
+during the execution phase. `run_state` is an empty Hash that's always
discarded at the end of a Chef Infra Client run.
For example, the following recipe will install the Apache web server,
@@ -520,7 +520,7 @@ end
where:
-- The **ruby_block** resource declares a `block` of Ruby code that is
+- The **ruby_block** resource declares a `block` of Ruby code that's
run during the execution phase of a Chef Infra Client run
- The `if` statement randomly chooses PHP or Perl, saving the choice
to `node.run_state['scripting_language']`
diff --git a/content/release_notes_360.md b/content/release_notes_360.md
index a692c43788..0da2c8220d 100644
--- a/content/release_notes_360.md
+++ b/content/release_notes_360.md
@@ -12,12 +12,116 @@ product = [""]
weight = 10
+++
-## Chef 360 Platform 1.0.2
+## Chef 360 Platform 1.1.2
+
+Release date: December 26, 2024.
-### Release details
+### New features
-- Version number: 1.0.2
-- Release date: July 22, 2024
+- In the Admin Console configuration UI, you can now set a public key expiration date for API gateways. The default date is December 31, 2030.
+
+### Improvements
+
+- Updated system-defined roles with the correct API endpoints.
+
+### Bug fixes
+
+- Updated the default public key expiration date to December 31, 2030.
+ This fixes an issue where users couldn't create a new tenant or send e-mail to Mailpit.
+
+### Supported skill versions
+
+| Skill | Skill name | Habitat package | Version |
+|---------------------------|----------------------------|------------------------------------------|---------|
+| Node Management Agent | node-management-agent | chef-platform/node-management-agent | 1.0.3 |
+| Courier Runner | courier-runner | chef-platform/courier-runner | 1.4.4 |
+| Gohai | chef-gohai | chef-platform/chef-gohai | 1.0.3 |
+| Shell Interpreter | shell-interpreter | chef-platform/shell-interpreter | 1.0.3 |
+| Restart Interpreter | restart-interpreter | chef-platform/restart-interpreter | 1.0.2 |
+| Infra Client Interpreter | chef-client-interpreter. | chef-platform/chef-client-interpreter | 1.0.4 |
+| Inspec Interpreter | inspec-interpreter | chef-platform/inspec-interpreter | 1.0.4 |
+
+## Chef 360 Platform 1.1.1
+
+Release date: December 4, 2024.
+
+### New features
+
+- We replaced Mailhog, a local email testing service, with [Mailpit](https://mailpit.axllent.org/), which is a more secure service.
+
+ If you've been using Mailhog for email testing, update the port number to `31101` to use Mailpit.
+
+### Improvements
+
+- You can now select saved node lists and node filters to target Courier jobs using the Courier Job Wizard in the Chef 360 Platform UI.
+- You can now reuse job templates from existing Courier jobs to create a new Courier job in the Chef 360 Platform UI.
+
+## Chef 360 Platform 1.1.0
+
+Release date: November 21, 2024.
+
+### New features
+
+- RabbitMQ used for Chef Courier jobs now supports TLS-based communication.
+
+- We added the following system-defined roles:
+
+ - Tenant Admin
+ - Organization Admin
+ - Node Manager
+ - Courier Operator
+
+ Users with these roles can perform tenant management, organization management, node management, and Courier-specific actions.
+ You can also use these roles as a reference for creating custom roles and policies based on business needs of your organization.
+
+ See the [System roles](https://docs.chef.io/360/1.1/administration/system_roles) and [System policies](https://docs.chef.io/360/1.1/administration/system_policies) documentation for more information.
+
+- Added UI workflows to perform basic Courier job runs, manage nodes and filters and perform administrative actions. See the [Chef 360 Platform UI documentation](https://docs.chef.io/360/1.1/chef_360_ui) for more information.
+
+- Chef 360 Platform now requires users to load their license keys. Users can run Chef Courier jobs until the license expiration date, after which users must renew their license keys to continue running Courier jobs.
+
+### Improvements
+
+- Upgraded nginx to 1.26.2 to address the following CVEs:
+
+ - CVE-2024-32760
+ - CVE-2024-31079
+ - CVE-2024-35200
+ - CVE-2024-34161
+
+- Added an API to fetch global default settings.
+- You can now modify the number of Replicas for each service when deploying Chef 360 Platform. See the [install documentation](https://docs.chef.io/360/1.1/install/server/install#replicas-count) for more information.
+
+### Bug fixes
+
+- You can now redeploy Chef 360 Platform with updated configurations.
+- When downloading details of a job, the artifact URL is updated to HTTP or HTTPS dynamically in the artifact URL string based on the server configuration.
+- The payload for filtering by the enrollment level and health status attributes is now supported with operator and value fields similar to filtering by other attributes.
+
+ This change requires that all users running Chef 360 Platform 1.0.x must upgrade their skill versions on all nodes to versions supported in Chef 360 Platform version 1.1.
+ The previous release versions of these skills won't run if they're not updated.
+
+### Supported skill versions
+
+| Skill | Skill name | Habitat package | Version |
+| -------------------------|---------------------------|---------------------------------------------------------------------------------------------------------------|----------|
+| Node Management Agent | `node-management-agent` | [chef-platform/node-management-agent](https://bldr.habitat.sh/#/pkgs/chef-platform/node-management-agent) | 1.0.3 |
+| Courier Runner | `courier-runner` | [chef-platform/courier-runner](https://bldr.habitat.sh/#/pkgs/chef-platform/courier-runner) | 1.4.4 |
+| Gohai | `chef-gohai` | [chef-platform/chef-gohai](https://bldr.habitat.sh/#/pkgs/chef-platform/chef-gohai) | 1.0.3 |
+| Shell Interpreter | `shell-interpreter` | [chef-platform/shell-interpreter](https://bldr.habitat.sh/#/pkgs/chef-platform/shell-interpreter) | 1.0.3 |
+| Restart Interpreter | `restart-interpreter` | [chef-platform/restart-interpreter](https://bldr.habitat.sh/#/pkgs/chef-platform/restart-interpreter) | 1.0.2 |
+| Infra Client Interpreter | `chef-client-interpreter` | [chef-platform/chef-client-interpreter](https://bldr.habitat.sh/#/pkgs/chef-platform/chef-client-interpreter) | 1.0.4 |
+| Inspec Interpreter | `inspec-interpreter` | [chef-platform/inspec-interpreter](https://bldr.habitat.sh/#/pkgs/chef-platform/inspec-interpreter) | 1.0.4 |
+
+### Known issues
+
+- Re-enrolling a node that's already enrolled to the same organization or a different organization isn't currently supported.
+ A node must be unenrolled manually if you want to re-enroll.
+- Evidence (log) files are downloaded without the `.zip` extension from the run details screen.
+
+## Chef 360 Platform 1.0.2
+
+Release date: July 22, 2024.
### Bug fixes
@@ -39,14 +143,11 @@ product = [""]
## Chef 360 Platform 1.0.1
-### Release details
-
-- Version number: 1.0.1
-- Release date: July 15, 2024
+Release date: July 15, 2024
### Improvements
-- In the previous release, you could not add more than one user-defined policy to a custom role.
+- In the previous release, you couldn't add more than one user-defined policy to a custom role.
You can now create custom roles with multiple policies with a single command.
- The Courier Orchestrator service is now multi-threaded so that it can send multiple Courier jobs that are scheduled simultaneously.
- We improved Chef 360 Platform enrollment failure messages so that they now show appropriate error messages for all stages of enrollment.
@@ -72,20 +173,17 @@ product = [""]
## Chef 360 Platform 1.0.0
-### Release details
-
-- Version number: 1.0.0
-- Release date: July 2, 2024
+Release date: July 2, 2024.
### Overview
-This is the initial release of Progress Chef 360 Platform. Chef 360 Platform is a set of integrated software components and a surrounding ecosystem where value comes not only from individual features but from its ability to connect external tools, teams, data, and processes. We see Chef 360 Platform as a way to take the power and benefits of policy as code and spread it to everyone who has a role in development, operations and security. In addition to that Chef 360 Platform is an integrated ecosystem of tools providing not just value but also its ability to connect teams and tools together. It is a modern, cloud-native DevOps platform that democratizes DevOps by empowering IT operators and DevOps engineers to manage mission-critical infrastructure securely.
+This is the initial release of Progress Chef 360 Platform. Chef 360 Platform is a set of integrated software components and a surrounding ecosystem where value comes not only from individual features but from its ability to connect external tools, teams, data, and processes. We see Chef 360 Platform as a way to take the power and benefits of policy as code and spread it to everyone who has a role in development, operations and security. In addition to that Chef 360 Platform is an integrated ecosystem of tools providing not just value but also its ability to connect teams and tools together. It's a modern, cloud-native DevOps platform that democratizes DevOps by empowering IT operators and DevOps engineers to manage mission-critical infrastructure securely.
When we set out to build a new platform we identified four primary guiding principles, used to help us make the right choices and stay aligned with our objectives.
- Automate everything (within reason), by providing you prescriptive ways to use the platform, while still retaining our core flexibility.
- Reach everywhere, be that your data center, a cloud, a laptop, single board computer or even a satellite. We want to support you everywhere you are running a workload.
-- Embrace all users and skill levels. So we are making this platform not just with APIs and CLIs for automation but also with an intuitive UI.
+- Embrace all users and skill levels. So we're making this platform not just with APIs and CLIs for automation but also with an intuitive UI.
- Embrace open standards. This means you get open interoperability to OpenAPI v3 services, cloud-native benefits by starting in Kubernetes at Chef 360's inception, and other security standards to make acceptance and adoption easy.
Chef 360 Platform contains a host of services on which new products from Chef are being built. Progress Chef Courier is one such product. This release also is the initial release of Progress Chef Courier product.
@@ -96,7 +194,7 @@ This functionality empowers practitioners to execute ad hoc and unplanned duties
### Major services
-Chef 360 Platform comes packaged with the following major categories of services. Each of these categories serves a very specific purpose in enabling the end-to-end functioning of every product made accessible through the Chef 360 Platform.
+Chef 360 Platform comes packaged with the following major categories of services. Each of these categories serves a very specific purpose in enabling the end-to-end functioning of every product made accessible through Chef 360 Platform.
- Courier including services for scheduling, orchestrating, delivering and tracking state for jobs
- Node management including centralized services and enrollment
@@ -133,7 +231,7 @@ Interface-driven
### Supported platforms
1. The Chef 360 Platform is a set of containers which run on standard Kubernetes environments. Most containers are 'scratch' containers and run on the default pod provided by the host. Some containers are on Debian base images. The Chef 360 Platform v1.0 release is packaged inside and is tested on a `k0s` distribution.
-1. The Chef 360 Platform has three command-line interfaces which run on versions of Linux, Microsoft Windows, and MacOS on x86 or ARM architectures (as appropriate). These are available in the bundled tools container in the Chef 360 Platform distribution.
+1. The Chef 360 Platform has three command-line interfaces which run on versions of Linux, Windows, and MacOS on x86 or ARM architectures (as appropriate). These are available in the bundled tools container in the Chef 360 Platform distribution.
1. The Chef 360 Platform has three agents: the Habitat base module, a Node Management agent, and a Courier agent. The Habitat installer runs on all platforms indicated on the [Chef Habitat downloads page](https://community.chef.io/downloads/tools/habitat) (or your support portal if you have a commercial Chef license). We tested with the latest version of Habitat for this release. The agents are available in the bundled tools container in the Chef 360 Platform distribution.
1. Chef 360 Platform relies on the following infrastructure components for its services:
@@ -159,16 +257,16 @@ Interface-driven
### Known issues
-We have tested on the supported platforms listed above and intend on broadening this support in upcoming releases. Chef 360 Platform may operate correctly on other platforms; we just cannot guarantee it. Contact your customer success team with questions.
+We've tested on the supported platforms listed above and intend on broadening this support in upcoming releases. Chef 360 Platform may operate correctly on other platforms; we just can't guarantee it. Contact your customer success team with questions.
Chef 360 Platform has the following known issues:
-- The Chef 360 Platform is not yet supported for environments which cannot access the internet, that is, air gapped environments.
+- The Chef 360 Platform isn't yet supported for environments which can't access the internet, that's, air gapped environments.
- Don't create a tenant name with the underscore character `_`, services will fail to start.
-- Don't change or modify the underlying Kubernetes configuration after installing v1.0; upgrades are not yet supported.
-- Upgrades to v1.0 are manual; automatic upgrades are not supported.
-- The message queues internally for Chef Courier job distribution and node enrollment do not support TLS.
-- Chef 360 Platform services do not work correctly on nodes using localhost DNS settings (`127.0.0.1`).
+- Don't change or modify the underlying Kubernetes configuration after installing v1.0; upgrades aren't yet supported.
+- Upgrades to v1.0 are manual; automatic upgrades aren't supported.
+- The message queues internally for Chef Courier job distribution and node enrollment don't support TLS.
+- Chef 360 Platform services don't work correctly on nodes using localhost DNS settings (`127.0.0.1`).
- Some Courier jobs run to completion---success or failure---and may not be cancellable. Additionally, if a Linux shell job is specified for a Windows node (or vice-versa), it should be manually verified as working since some scripts may have 3rd party dependencies on a given platform.
- Several features including node filters and exemptions, un-enrolling and re-enrolling a node, and multi-node deployment under development and will be available in a subsequent release.
- The user experience (UI) is experimental and being updated frequently now so some users of the distribution channel and containers may see improvements and screen changes between operations.
diff --git a/content/release_notes_chefdk.md b/content/release_notes_chefdk.md
index 2a42685958..d4204c66cd 100644
--- a/content/release_notes_chefdk.md
+++ b/content/release_notes_chefdk.md
@@ -36,7 +36,7 @@ ChefDK packages are no longer produced for Debian 8 and RHEL/CentOS 6, as these
#### Test Kitchen
-Test Kitchen was updated from 2.7.2 to 2.8.0. This release improves how we execute commands on Windows hosts to avoid failures from executing commands that are too long for the windows command line. Thanks for this fix [@ramereth](https://github.com/ramereth)!
+Test Kitchen was updated from 2.7.2 to 2.8.0. This release improves how we execute commands on Windows hosts to avoid failures from executing commands that are too long for the Windows command line. Thanks for this fix [@ramereth](https://github.com/ramereth)!
#### Kitchen Google
@@ -44,7 +44,7 @@ The Kitchen Google driver for Test Kitchen was updated from 2.0.3 to 2.1.0. This
#### Kitchen Vagrant
-The kitchen-vagrant plugin is updated from version 1.7.1 to 1.7.2 with a bug fix to no longer stop with an error when updating a Vagrant box that has not yet been downloaded.
+The kitchen-vagrant plugin is updated from version 1.7.1 to 1.7.2 with a bug fix to no longer stop with an error when updating a Vagrant box that hasn't yet been downloaded.
#### Kitchen Dokken
@@ -54,12 +54,12 @@ Kitchen Dokken has been updated to 2.11.2 to resolve failures from creating cont
Chef InSpec has been updated to 4.24.8, which includes the following improvements:
-- An unset `HOME` environment variable will not cause execution failures
+- An unset `HOME` environment variable won't cause execution failures
- You can use wildcards in `platform-name` and `release` in InSpec profiles. Thanks for this improvement [@yarick](https://github.com/yarick)!
- The `WMI` resource now returns an array to support returning multiple WMI objects
- The `package` resource on Windows properly escapes package names. Thanks for this improvement [@ramereth](https://github.com/ramereth)!
- The `grub_conf` resource succeeds even if without a `menuentry` in the grub config
-- Loaded plugins will not try to re-load themselves
+- Loaded plugins won't try to re-load themselves
- Waiver expiration is now always populated
#### chef-vault
@@ -133,7 +133,7 @@ The `chef-vault` gem has been updated from 4.0.11 to 4.0.12. This release fixes
### Knife Improvements
-We have reworked how the knife command loads dependencies to greatly improve performance. For some users this may result in a 2/3 reduction in the time knife commands take to load the first time. We also fixed the `knife ssh` command hanging when connecting to Windows nodes over SSH.
+We've reworked how the knife command loads dependencies to greatly improve performance. For some users this may result in a 2/3 reduction in the time knife commands take to load the first time. We also fixed the `knife ssh` command hanging when connecting to Windows nodes over SSH.
### Updates Components
@@ -154,7 +154,7 @@ Chef Vault has been updated from 4.0.1 to 4.0.11. This release resolves errors w
#### Test Kitchen
-Test Kitchen has been updated from 2.5.4 to 2.7.0, which adds the ability to mark plugins as unable to run with a concurrency (`-c`) level greater than 1. This will help prevent strange failures that occur with some plugins which cannot run concurrently in the future.
+Test Kitchen has been updated from 2.5.4 to 2.7.0, which adds the ability to mark plugins as unable to run with a concurrency (`-c`) level greater than 1. This will help prevent strange failures that occur with some plugins which can't run concurrently in the future.
#### Kitchen AzureRM
@@ -188,7 +188,7 @@ The included `cacerts` bundle in Chef Infra Client has been updated to the 7-22-
#### Chef Infra Client
-Chef Infra Client has been updated from 15.12.2 to 15.3.8. This new release includes a new deprecation warning when resources specify `resource_name` without also specifying `provides` which results in failures on Chef Infra Client 16.2 and later. This release also improves the warning message that occurs when a cookbook includes a resource that is now bundled directly in Chef Infra Client.
+Chef Infra Client has been updated from 15.12.2 to 15.3.8. This new release includes a new deprecation warning when resources specify `resource_name` without also specifying `provides` which results in failures on Chef Infra Client 16.2 and later. This release also improves the warning message that occurs when a cookbook includes a resource that's now bundled directly in Chef Infra Client.
#### Chef InSpec
@@ -247,7 +247,7 @@ InSpec was updated from 4.19 to 4.21. This new release includes the following im
The `knife bootstrap` command has been updated with several fixes and improvements
-- knife bootstrap will now warn when bootstrapping a system using a validation key. Users should instead use validatorless bootstrapping with `knife bootstrap` which generates node and client keys using the client key of the user bootstrapping the node. This method is far more secure as an organization-wide validation key does not need to be distributed or rotated. Users can switch to validatorless bootstrapping by removing any `validation_key` entries in their config.rb (knife.rb) file.
+- knife bootstrap will now warn when bootstrapping a system using a validation key. Users should instead use validatorless bootstrapping with `knife bootstrap` which generates node and client keys using the client key of the user bootstrapping the node. This method is far more secure as an organization-wide validation key doesn't need to be distributed or rotated. Users can switch to validatorless bootstrapping by removing any `validation_key` entries in their config.rb (knife.rb) file.
- Resolved an error bootstrapping Linux nodes from Windows hosts
- Improved information messages during the bootstrap process
- Bootstrapping will now be done using a single SSH connection improving bootstrap times on high latency network connection.
@@ -284,7 +284,7 @@ Sample kitchen.yml config:
### New Platforms
-ChefDK packages are now created for Ubuntu 20.04 and Debian 10! Additionally, we have increased package validation for our Windows 10 packages to ensure compatibility. See the Chef Downloads Page for a complete list of platforms.
+ChefDK packages are now created for Ubuntu 20.04 and Debian 10! Additionally, we've increased package validation for our Windows 10 packages to ensure compatibility. See the Chef Downloads Page for a complete list of platforms.
### macOS Binary Signing
@@ -325,7 +325,7 @@ Cookstyle has upgraded from 5.20 to 5.23, which includes 8 new cops, and signifi
- ChefRedundantCode/StringPropertyWithNilDefault
- ChefRedundantCode/PropertySplatRegex
-**Note**: Chef Workstation ships with Cookstyle 6.x, which includes a significantly improved RuboCop engine, and 24 additional cops for resolving deprecations and preparing cookbooks for Chef Infra Client 16. Cookstyle 5.x does not include Chef Infra Client 16 preparation cops.
+**Note**: Chef Workstation ships with Cookstyle 6.x, which includes a significantly improved RuboCop engine, and 24 additional cops for resolving deprecations and preparing cookbooks for Chef Infra Client 16. Cookstyle 5.x doesn't include Chef Infra Client 16 preparation cops.
#### Test Kitchen
@@ -347,7 +347,7 @@ The Kitchen Hyper-V driver has updated from 0.5.3 to 0.5.4, which resolves failu
**Kitchen DigitalOcean**
-The Kitchen DigitalOcean driver has updated from 0.10.5 to 0.11.0. This release adds slugs for Ubuntu 20.04 / RHEL 8 / Fedora 31 support, increases the the default instance memory size to 1GB, and adds support for VPCs. Thanks [@zmaupin](https://github.com/zmaupin), [@tolland](https://github.com/tolland), and [@gregf](https://github.com/gregf) for these improvements.
+The Kitchen DigitalOcean driver has updated from 0.10.5 to 0.11.0. This release adds slugs for Ubuntu 20.04 / RHEL 8 / Fedora 31 support, increases the default instance memory size to 1GB, and adds support for VPCs. Thanks [@zmaupin](https://github.com/zmaupin), [@tolland](https://github.com/tolland), and [@gregf](https://github.com/gregf) for these improvements.
**Kitchen EC2**
@@ -359,7 +359,7 @@ The Kitchen InSpec verifier has updated to allow setting Chef InSpec plugins for
**Kitchen Dokken**
-The Kitchen Dokken driver has updated from 2.8.1 to 2.9.0. This release adds a new provisioning configuration, `clean_dokken_sandbox`, that does not require cleaning the Chef Infra and Test Kitchen files between converges. This configuration will speed up repeatedly converging systems. This defaults to `true` which maintains the existing behavior. Thanks [@chrisUsick](https://github.com/chrisUsick).
+The Kitchen Dokken driver has updated from 2.8.1 to 2.9.0. This release adds a new provisioning configuration, `clean_dokken_sandbox`, that doesn't require cleaning the Chef Infra and Test Kitchen files between converges. This configuration will speed up repeatedly converging systems. This defaults to `true` which maintains the existing behavior. Thanks [@chrisUsick](https://github.com/chrisUsick).
#### Knife Plugins
@@ -407,7 +407,7 @@ libarchive has updated from 3.4.0 to 3.4.2 to resolve multiple security vulnerab
**OpenSSL**
-openSSL has updated from 1.0.2u to 1.0.2v, which does not address any particular CVEs, but includes multiple security hardening updates.
+openSSL has updated from 1.0.2u to 1.0.2v, which doesn't address any particular CVEs, but includes multiple security hardening updates.
**Rake**
@@ -452,7 +452,7 @@ AllCops:
Cookstyle now includes two new Chef cop departments with a large number of existing cops moved into these more appropriate departments. Our goal is to have clearly defined cop departments that can be enabled or disabled to detect particular conditions in your cookbooks. Cops in the new ChefSharing department are focused around sharing cookbooks internally or on the public Supermarket. This includes things like ensuring proper license strings and complete metadata. Cops in the ChefRedundantCode category detect and correct unnecessary cookbook code. Anything detected by ChefRedundantCode cops can be removed regardless of the Chef Infra Client release you run in your infrastructure, so these are always safe to run.
-With the addition of these new departments, we have moved many cops out of the ChefCorrectness department. Going forward only cops that detect code that may fail a Chef Infra Client run or cause it to behave incorrectly will be included in this category. We hope that ChefCorrectness along with ChefDeprecations are used in most cookbook CI pipelines.
+With the addition of these new departments, we've moved many cops out of the ChefCorrectness department. Going forward only cops that detect code that may fail a Chef Infra Client run or cause it to behave incorrectly will be included in this category. We hope that ChefCorrectness along with ChefDeprecations are used in most cookbook CI pipelines.
#### kitchen-azurerm
@@ -564,7 +564,7 @@ AllCops:
Cookstyle now includes two new Chef cop departments with a large number of existing cops moved into these more appropriate departments. Our goal is to have clearly defined cop departments that can be enabled or disabled to detect particular conditions in your cookbooks. Cops in the new ChefSharing department are focused around sharing cookbooks internally or on the public Supermarket. This includes things like ensuring proper license strings and complete metadata. Cops in the ChefRedundantCode category detect and correct unnecessary cookbook code. Anything detected by ChefRedundantCode cops can be removed regardless of the Chef Infra Client release you run in your infrastructure, so these are always safe to run.
-With the addition of these new departments, we have moved many cops out of the ChefCorrectness department. Going forward only cops that detect code that may fail a Chef Infra Client run or cause it to behave incorrectly will be included in this category. We hope that ChefCorrectness along with ChefDeprecations are used in most cookbook CI pipelines.
+With the addition of these new departments, we've moved many cops out of the ChefCorrectness department. Going forward only cops that detect code that may fail a Chef Infra Client run or cause it to behave incorrectly will be included in this category. We hope that ChefCorrectness along with ChefDeprecations are used in most cookbook CI pipelines.
#### kitchen-azurerm
@@ -651,7 +651,7 @@ resource:
Chef Infra Client now includes a new `chef-utils` gem which ships with a
large number of helpers to make writing cookbooks easier. Many of these
-helpers existed previously in the `chef-sugar` gem. We have renamed many
+helpers existed previously in the `chef-sugar` gem. We've renamed many
of the named helpers for consistency while providing backwards
compatibility with existing `chef-sugar` names. Existing cookbooks
written with `chef-sugar` should work unmodified with any of these new
@@ -664,12 +664,12 @@ readme](https://github.com/chef/chef/blob/master/chef-utils/README.md).
**Chefignore Improvements**
-We have reworked how chefignore files are handled in `knife` which has
+We've reworked how chefignore files are handled in `knife` which has
allowed us to close out a large number of long outstanding bugs. `knife`
will now traverse all the way up the directory structure looking for a
chefignore file. This means you can place a chefignore file in each
cookbook or any parent directory in your repository structure.
-Additionally, we have made fixes that ensure that commands like
+Additionally, we've made fixes that ensure that commands like
`knife diff` and `knife cookbook upload` always honor your chefignore
files.
@@ -677,14 +677,14 @@ files.
The new `chef_sleep` resource can be used to sleep for a specified
number of seconds during a Chef Infra Client run. This may be helpful to
-use with other commands that return a completed status before they are
-actually ready. In general, do not use this resource unless you truly
+use with other commands that return a completed status before they're
+actually ready. In general, don't use this resource unless you truly
need it.
-Using with a Windows service that starts, but is not immediately ready:
+Using with a Windows service that starts, but isn't immediately ready:
> ```ruby
-> service 'Service that is slow to start and reports as started' do
+> service 'Service that's slow to start and reports as started' do
> service_name 'my_database'
> action :start
> notifies :sleep, chef_sleep['wait for service start']
@@ -805,7 +805,7 @@ vulnerabilities:
### Habitat Packages
-We are now publishing Habitat packages for ChefDK 4. See
+We're now publishing Chef Habitat packages for ChefDK 4. See
[chef/chef-dk](https://bldr.habitat.sh/#/pkgs/chef/chef-dk) on Habitat
Depot for a complete list of available versions.
@@ -826,7 +826,7 @@ changes:
**New Features**
-- We have released our beta Chef InSpec plug-in for HashiCorp Vault.
+- We've released our beta Chef InSpec plug-in for HashiCorp Vault.
Check it out in our [inspec-vault GitHub
repo](https://github.com/inspec/inspec-vault) and let us know what
you think -- or better yet, start jumping in and contributing with
@@ -963,7 +963,7 @@ for a complete list of cops included in Cookstyle 5.6.
Going forward, Cookstyle will be our sole Ruby and Chef Infra cookbook
linting tool. With the release of Cookstyle 5.6, we're officially
-deprecating Foodcritic and will not be shipping Foodcritic in the next
+deprecating Foodcritic and won't be shipping Foodcritic in the next
major release of Chef Workstation (April 2020). See our [Goodbye,
Foodcritic blog post](https://blog.chef.io/goodbye-foodcritic/) for more
information on why Cookstyle is replacing Foodcritic.
@@ -1034,7 +1034,7 @@ coreos-beta-2247-2-0-v20190911 coreos-cloud coreos-beta 9 GB READY
Git has been updated from 2.20.0 to 2.23.0 on Windows and from 2.14.1 to
2.23.0 on non-Windows systems. This brings the latest git workflows to
-our users who do not have it installed another way and fixes two CVEs:
+our users who don't have it installed another way and fixes two CVEs:
- non-Windows systems:
[CVE-2017-14867](https://www.cvedetails.com/cve/CVE-2017-14867/)
@@ -1093,11 +1093,11 @@ changes:
Cookstyle has been updated from 5.0 to 5.1.19 with twenty-four new Chef
specific cops to detect, and in many cases, to autocorrect errors in
-your cookbook code. With the release of Cookstyle 5.1, we have started
+your cookbook code. With the release of Cookstyle 5.1, we've started
the process of replacing Foodcritic with Cookstyle. Cookstyle offers a
modern configuration system, autocorrection, and a faster and more
reliable engine thanks to RuboCop. We will continue to port useful rules
-from Foodcritic to Cookstyle, as well as add rules that were not
+from Foodcritic to Cookstyle, as well as add rules that weren't
possible in the legacy Foodcritic engine. See the [Cookstyle 5.1 Release
Notes](https://github.com/chef/cookstyle/blob/main/RELEASE_NOTES.md#cookstyle-51)
for a complete list of new rules.
@@ -1286,7 +1286,7 @@ distros and additional configuration options for instance setup. You can
now control the default DigitalOcean region systems that are spun up by
using a new `DIGITALOCEAN_REGION` env var. You can still modify the
region in the driver section of your `kitchen.yml` file if you'd like,
-and the default region of `nyc1` has not changed. This release also adds
+and the default region of `nyc1` hasn't changed. This release also adds
slug support for `fedora-29`, `fedora-30`, and `ubuntu-19`. Finally, if
you'd like to monitor your test instances, the new `monitoring`
configuration option in the `kitchen.yml` driver section allows enabling
@@ -1366,7 +1366,7 @@ subnet-ba1135c9 available 172.31.16.0/20 us-west-2a 4091 Yes
### Platform Support Updates
Ubuntu 14.04 entered the end-of-life phase April 30, 2019. Since this
-version of Ubuntu is now end-of-life, we have stopped building packages
+version of Ubuntu is now end-of-life, we've stopped building packages
for Ubuntu 14.04. If you rely on Ubuntu 14.04 in your environment, we
highly recommend upgrading your host to Ubuntu 16.04 or 18.04.
@@ -1404,7 +1404,7 @@ change.
Chef Provisioning is no longer included with ChefDK, and will be
officially end of life on August 31, 2019. The source code of Chef
Provisioning and the drivers have been moved into the chef-boneyard
-GitHub organization and will not be further maintained. Current users of
+GitHub organization and won't be further maintained. Current users of
Chef Provisioning should contact your Chef Customer Success Manager or
Account Representative to review your options.
@@ -1457,7 +1457,7 @@ repositories that match Chef's best practices.
Infra Client releases as `require_chef_omnibus` will be removed in
the next major Test Kitchen release.
- `chef generate cookbook_file` no longer places the specified file
- in a "default" folder as these are not needed in Chef Infra Client
+ in a "default" folder as these aren't needed in Chef Infra Client
12 and later.
- `chef generate repo` no longer outputs the full Chef Infra Client
run information while generating the repository. Similar to the
@@ -1687,7 +1687,7 @@ shipped in ChefDK 4 have been backported to ChefDK 3.
Client releases as `require_chef_omnibus` will be removed in the
next major Test Kitchen release.
- `chef generate cookbook_file` no longer places the specified file in
- a `default` folder as these are not needed in Chef Infra Client 12
+ a `default` folder as these aren't needed in Chef Infra Client 12
and later.
- `chef generate cookbook` now generates cookbooks with updated
`.gitignore` and `chefignore` files
@@ -1724,7 +1724,7 @@ distros and additional configuration options for instance setup. You can
now control the default DigitalOcean region systems that are spun up by
using a new `DIGITALOCEAN_REGION` environmental variable. You can still
modify the region in the driver section of your `kitchen.yml` file if
-you'd like, and the default region of `nyc1` has not changed. This
+you'd like, and the default region of `nyc1` hasn't changed. This
release also adds slug support for `fedora-29`, `fedora-30`, and
`ubuntu-19`. Finally, if you'd like to monitor your test instances, the
new `monitoring` configuration option in the `kitchen.yml` driver
@@ -1874,10 +1874,10 @@ non-breaking Test Kitchen 2.0 features:
### New Policy File Functionality
-`include_policy` now supports `:remote` policy files. This new
-functionality allows you to include policy files over http. Remote
-policy files require remote cookbooks and `install` will fail otherwise
-if the included policy file includes cookbooks with paths. Thanks
+`include_policy` now supports `:remote` Policyfiles. This new
+functionality allows you to include Policyfiles over http. Remote
+Policyfiles require remote cookbooks and `install` will fail otherwise
+if the included Policyfile includes cookbooks with paths. Thanks
[mattray](https://github.com/mattray)!
### Updated Components
@@ -2004,7 +2004,7 @@ what's new.
### Deprecations
Chef Provisioning has been in maintenance mode since 2015 and due to the
-age of its dependencies it cannot be included in ChefDK 4 which is
+age of its dependencies it can't be included in ChefDK 4 which is
scheduled for an April 2019 release.
## What's New in 3.6
@@ -2083,7 +2083,7 @@ what's new.
#### stove 7.0.1
- The yank command has been removed as this command causes large
- downstream impact to other users and should not be part of the
+ downstream impact to other users and shouldn't be part of the
tooling
- The metadata.rb file will now be included in uploads to match the
behavior of berkshelf 7+
@@ -2194,7 +2194,7 @@ what's new.
### Smaller Package Size
ChefDK RPM and Debian packages are now compressed. Additionally many
-gems were updated to remove extraneous files that do not need to be
+gems were updated to remove extraneous files that don't need to be
included. The download size of packages has decreased accordingly (all
measurements in megabytes):
@@ -2210,9 +2210,9 @@ Chef Downloads.
Ruby has been updated to 2.5.3 to resolve the following vulnerabilities:
-- \`CVE-2018-16396\`: Tainted flags are not propagated in Array\#pack
+- \`CVE-2018-16396\`: Tainted flags aren't propagated in Array\#pack
and String\#unpack with some directives
-- \`CVE-2018-16395\`: OpenSSL::X509::Name equality check does not work
+- \`CVE-2018-16395\`: OpenSSL::X509::Name equality check doesn't work
correctly
## What's New in 3.3
@@ -2247,16 +2247,16 @@ for examples of the new syntax.
The Chef CLI now includes a new option: chef
update --exclude-deps for policyfiles which will only update the
-cookbook(s) given on the command line.
+cookbooks given on the command line.
### Deprecations
-- `chef generate app` - Application repos were a pattern that did not
+- `chef generate app` - Application repos were a pattern that didn't
take off.
- `chef generate lwrp` - Use chef generate
resource. Every supported release of Chef supports custom
resources. Custom resources are awesome. No one should be writing
- new LWRPs any more. LWRPS are not awesome.
+ new LWRPs any more. LWRPS aren't awesome.
## What's New in 3.2
@@ -2270,7 +2270,7 @@ cookbook(s) given on the command line.
- New chef describe-cookbook
command to display the cookbook checksum.
- - Change policyfile generator to use `policyfiles` directory
+ - Change Policyfile generator to use `policyfiles` directory
instead of `policies` directory
- **New Tooling**
@@ -2363,7 +2363,7 @@ cookbook(s) given on the command line.
**Test Kitchen 1.22**
- Added a new `ssh_gateway_port` config.
- - Fixed a bug on Unix systems where scripts are not created as
+ - Fixed a bug on Unix systems where scripts aren't created as
executable.
- **Other Updated Components and Tools**
@@ -2512,7 +2512,7 @@ cookbook(s) given on the command line.
- **Rename smoke tests to integration tests**
The cookbook, recipe, and app generators now name the test directory
- `integration` instead of `smoke`. This will not impact existing
+ `integration` instead of `smoke`. This won't impact existing
cookbooks generated with older releases of ChefDK, but it does
simplify the `.kitchen.yml` configuration for all new cookbooks.
@@ -2593,12 +2593,12 @@ cookbook(s) given on the command line.
Policyfile can use the `include_policy` directive as described in
[RFC097](https://github.com/chef/chef-rfc/blob/master/rfc097-policyfile-includes.md).
- This directive's purpose is to allow the inclusion policyfile locks
+ This directive's purpose is to allow the inclusion Policyfile locks
to the current policyfile. In this iteration, we support sourcing
lock files from a local path or a Chef server. Below is a simple
example of how the `include_policy` directive can be used:
- Given a policyfile `base.rb`:
+ Given a Policyfile `base.rb`:
```ruby
name 'base'
@@ -2657,7 +2657,7 @@ cookbook(s) given on the command line.
```
This will produce a `users.lock.json` file that has the `base`
- policyfile lock merged in.
+ Policyfile lock merged in.
More information can be found in
[RFC097](https://github.com/chef/chef-rfc/blob/main/rfc097-policyfile-includes.md)
@@ -2665,7 +2665,7 @@ cookbook(s) given on the command line.
- **New tools bundled**
- We are now shipping these tools as part of ChefDK:
+ We're now shipping these tools as part of ChefDK:
- [kitchen-digitalocean](https://github.com/test-kitchen/kitchen-digitalocean)
- [kitchen-google](https://github.com/test-kitchen/kitchen-google)
@@ -2777,11 +2777,11 @@ Chef 2.0.28 fixes an
### Chef Infra Client 13.2
Chef Infra Client 13 is the most delightful version of Chef Infra Client available.
-We have taken what we have learned from many bug reports, forum posts, and
-conversations with our users, and we have made it safer and easier than
-ever to write great cookbooks. We have also included a number of new
+We've taken what we've learned from many bug reports, forum posts, and
+conversations with our users, and we've made it safer and easier than
+ever to write great cookbooks. We've also included a number of new
resources that better support our most popular operating systems, and
-we have made it easier to write patterns that result in reusable,
+we've made it easier to write patterns that result in reusable,
efficient code.
Chef Infra Client 13.2 solves a number of issues that were reported in our
@@ -2810,9 +2810,9 @@ Berkshelf adds support for two new sources:
### Chef Vault 3.1
Chef Vault 3.1 includes a number of optimizations for large numbers of
-nodes. In most situations, we have seen at least 50% faster creation,
+nodes. In most situations, we've seen at least 50% faster creation,
update, and refresh operations, and much more efficient memory usage.
-We have also added a new `sparse` mode, which dramatically reduces the
+We've also added a new `sparse` mode, which dramatically reduces the
amount of network traffic that occurs as nodes decrypt vaults. A lot of
the scalability work has been built and tested by our friends at Criteo.
@@ -2831,8 +2831,8 @@ every version of Chef.
The release of Foodcritic 11 also marks the creation of the Foodcritic
org on [GitHub](https://github.com/foodcritic), which makes it easier to
-get involved in writing rules and contributing code. We are excited to
-start building more of a community around Foodcritic, and cannot wait to
+get involved in writing rules and contributing code. We're excited to
+start building more of a community around Foodcritic, and can't wait to
see what the community cooks up.
### InSpec 1.30
@@ -2925,7 +2925,7 @@ longer depend on the delivery_build or delivery-base cookbook. Instead,
the Test Kitchen instance will use ChefDK as the standard workflow
runner setup.
-The build cookbook generator will not overwrite your `config.json` or
+The build cookbook generator won't overwrite your `config.json` or
`project.toml` if they exist already on your project.
### ChefSpec 6.0
@@ -3030,7 +3030,7 @@ standard license strings.
- An optional `functional` phase.
- New `remote_file` option to specify a remote `project.toml`.
- The ability to run stages (collection of phases).
-- Fixed bug where the generated `project.toml` file did not include
+- Fixed bug where the generated `project.toml` file didn't include
the prefix chef exec for some phases.
- Project git remotes will now update automatically, if applicable,
based on the values in the `cli.toml` or options provided through
@@ -3143,7 +3143,7 @@ previously passed.
### New DCO tool included
-We have included a new DCO command-line tool that makes it easier to
+We've included a new DCO command-line tool that makes it easier to
contribute to projects like Chef that use the Developer Certificate of
Origin. The tool allows you to enable/disable DCO sign-offs for each
repository and also allows you to retroactively sign off all commits on
@@ -3166,8 +3166,8 @@ a branch. See for details.
### Version 1.0!
We're recognizing ChefDK's continued stability with the honor of a 1.0
-tag. There is nothing in this release that breaks backwards
-compatibility with previous installations of ChefDK: it is simply a
+tag. There isn'thing in this release that breaks backwards
+compatibility with previous installations of ChefDK: it's simply a
formal recognition of the stability of the product.
### Foodcritic
diff --git a/content/release_notes_client.md b/content/release_notes_client.md
index 608fb41fc5..c88a7ccb36 100644
--- a/content/release_notes_client.md
+++ b/content/release_notes_client.md
@@ -12,5 +12,5 @@ toc_layout = "release_notes_toc"
title = "Chef Infra Client"
identifier = "release_notes/release_notes_client.md Chef Infra Client"
parent = "release_notes"
- weight = 50
+ weight = 60
+++
diff --git a/content/release_notes_habitat_packages.md b/content/release_notes_habitat_packages.md
new file mode 100644
index 0000000000..f64517cd7f
--- /dev/null
+++ b/content/release_notes_habitat_packages.md
@@ -0,0 +1,760 @@
++++
+title = "Chef Habitat package release notes"
+draft = true
+
+product = ["habitat"]
+
+[menu]
+ [menu.release_notes]
+ title = "Chef Habitat packages"
+ identifier = "release_notes/Chef Habitat packages"
+ parent = "release_notes"
+ weight = 50
++++
+
+## LTS-2024
+
+Release Date: November 18, 2024
+
+Release Channel: LTS-2024
+
+### Linux x86 architecture
+
+| S.No | Origin | Package Name | Version | Ident |
+|------|--------|---------------------------|----------------------|----------------|
+| 1 | core | 7zip | 17.05 | 20241018012028 |
+| 2 | core | acl | 2.3.1 | 20241017110951 |
+| 3 | core | acl-stage1 | 2.3.1 | 20241017110454 |
+| 4 | core | alex | 3.5.1.0 | 20241018040246 |
+| 5 | core | alsa-lib | 1.2.11 | 20241018021114 |
+| 6 | core | apr | 1.7.4 | 20241018034729 |
+| 7 | core | apr-util | 1.6.3 | 20241018034920 |
+| 8 | core | attr | 2.5.1 | 20241017110906 |
+| 9 | core | attr-stage1 | 2.5.1 | 20241017110412 |
+| 10 | core | autoconf | 2.71 | 20241017123414 |
+| 11 | core | autogen | 5.18.16 | 20241018025349 |
+| 12 | core | automake | 1.16.5 | 20241017123506 |
+| 13 | core | avisynthplus | 3.7.3 | 20241017153800 |
+| 14 | core | aws-cli | 2.15.38 | 20241018035747 |
+| 15 | core | bash | 5.2.21 | 20241017111154 |
+| 16 | core | bash-static | 5.2.21 | 20241018035047 |
+| 17 | core | bats | 1.8.2 | 20241017123807 |
+| 18 | core | bc | 6.0.4 | 20241017162227 |
+| 19 | core | bdwgc | 8.2.6 | 20241018021306 |
+| 20 | core | bind | 9.18.27 | 20241017154529 |
+| 21 | core | binutils | 2.39 | 20241017105003 |
+| 22 | core | binutils-stage0 | 2.39 | 20241017085225 |
+| 23 | core | binutils-stage1 | 2.39 | 20241017095024 |
+| 24 | core | bison | 3.8.2 | 20241017110249 |
+| 25 | core | boost | 1.85.0 | 20241018011400 |
+| 26 | core | buildah | 1.37.3 | 20241017160033 |
+| 27 | core | build-tools-bash-static | 5.2.21 | 20241017075602 |
+| 28 | core | build-tools-binutils | 2.39 | 20241017072214 |
+| 29 | core | build-tools-bison | 3.8.2 | 20241017083430 |
+| 30 | core | build-tools-cacerts | 2023.12.12 | 20241017080946 |
+| 31 | core | build-tools-coreutils | 9.4 | 20241017071339 |
+| 32 | core | build-tools-diffutils | 3.8 | 20241017080202 |
+| 33 | core | build-tools-file | 5.42 | 20241017075952 |
+| 34 | core | build-tools-findutils | 4.9.0 | 20241017080036 |
+| 35 | core | build-tools-gawk | 5.3.0 | 20241017071640 |
+| 36 | core | build-tools-gcc | 12.2.0 | 20241017073424 |
+| 37 | core | build-tools-gcc-libs | 12.2.0 | 20241017080421 |
+| 38 | core | build-tools-gettext | 0.21 | 20241017083044 |
+| 39 | core | build-tools-glibc | 2.36 | 20241017070233 |
+| 40 | core | build-tools-gmp | 6.2.1 | 20241017072647 |
+| 41 | core | build-tools-grep | 3.8 | 20241017071747 |
+| 42 | core | build-tools-gzip | 1.13 | 20241017080307 |
+| 43 | core | build-tools-isl | 0.25 | 20241017072837 |
+| 44 | core | build-tools-libmpc | 1.2.1 | 20241017073132 |
+| 45 | core | build-tools-libstdcxx | 12.2.0 | 20241017070958 |
+| 46 | core | build-tools-linux-headers | 5.19.8 | 20241017064735 |
+| 47 | core | build-tools-m4 | 1.4.19 | 20241017082909 |
+| 48 | core | build-tools-make | 4.4.1 | 20241017071904 |
+| 49 | core | build-tools-mpfr | 4.1.0 | 20241017073014 |
+| 50 | core | build-tools-ncurses | 6.4 | 20241017082154 |
+| 51 | core | build-tools-openssl | 3.0.9 | 20241017081602 |
+| 52 | core | build-tools-patch | 2.7.6 | 20241017073215 |
+| 53 | core | build-tools-patchelf | 0.18.0 | 20241017081046 |
+| 54 | core | build-tools-perl | 5.36.0 | 20241017084104 |
+| 55 | core | build-tools-python | 3.10.8 | 20241017083544 |
+| 56 | core | build-tools-rust | 1.79.0 | 20241017081123 |
+| 57 | core | build-tools-sed | 4.9 | 20241017071946 |
+| 58 | core | build-tools-tar | 1.35 | 20241017072048 |
+| 59 | core | build-tools-texinfo | 6.8 | 20241017084355 |
+| 60 | core | build-tools-toml-cli | 0.2.3 | 20241017081455 |
+| 61 | core | build-tools-util-linux | 2.38.1 | 20241017104207 |
+| 62 | core | build-tools-wget | 1.21.3 | 20241017082014 |
+| 63 | core | build-tools-xz | 5.2.6 | 20241017073319 |
+| 64 | core | build-tools-zlib | 1.3.1 | 20241017081015 |
+| 65 | core | bundler | 2.5.19 | 20241018003056 |
+| 66 | core | busybox | 1.36.1 | 20241018020713 |
+| 67 | core | busybox-static | 1.36.1 | 20241017124523 |
+| 68 | core | bzip2 | 1.0.8 | 20241017112023 |
+| 69 | core | bzip2-stage0 | 1.0.8 | 20241017085145 |
+| 70 | core | cabal-install | 3.12.1.0 | 20241017163244 |
+| 71 | core | cacerts | 2023.12.12 | 20241017111624 |
+| 72 | core | cairo | 1.18.0 | 20241017145413 |
+| 73 | core | certstrap | 1.3.0 | 20241018043504 |
+| 74 | core | check | 0.15.2 | 20241018041058 |
+| 75 | core | cmake | 3.25.1 | 20241017132348 |
+| 76 | core | cmake-stage1 | 3.25.1 | 20241017124828 |
+| 77 | core | coreutils | 9.4 | 20241017111752 |
+| 78 | core | coreutils-stage1 | 9.4 | 20241017110631 |
+| 79 | core | corretto | 11.0.23.9.1 | 20241018050217 |
+| 80 | core | cpanminus | 1.7047 | 20241017160335 |
+| 81 | core | cunit | 3.2.7 | 20241017125346 |
+| 82 | core | curl | 8.7.1 | 20241017131032 |
+| 83 | core | cyrus-sasl | 2.1.28 | 20241018024847 |
+| 84 | core | db | 5.3.28 | 20241018024940 |
+| 85 | core | dbus | 1.14.10 | 20241018004356 |
+| 86 | core | dejagnu | 1.6.3 | 20241017114323 |
+| 87 | core | dejagnu-stage1 | 1.6.3 | 20241017104903 |
+| 88 | core | devicemapper | 2.03.26 | 20241018005546 |
+| 89 | core | dex | 2.38.0 | 20241017135135 |
+| 90 | core | diffutils | 3.8 | 20241017113404 |
+| 91 | core | docker | 26.0.0 | 20241017160704 |
+| 92 | core | dotnet- | core | 8.0.8 |
+| 93 | core | doxygen | 1.11.0 | 20241018032314 |
+| 94 | core | dpkg | 1.22.11 | 20241018045321 |
+| 95 | core | e2fsprogs | 1.46.4 | 20241017131930 |
+| 96 | core | elfutils | 0.191 | 20241018050650 |
+| 97 | core | erlang26 | 26.2.2 | 20241017154809 |
+| 98 | core | expat | 2.6.2 | 20241017125425 |
+| 99 | core | expect | 5.45.4 | 20241017112705 |
+| 100 | core | expect-stage1 | 5.45.4 | 20241017104806 |
+| 101 | core | ffmpeg | 7.0.2 | 20241017153858 |
+| 102 | core | file | 5.42 | 20241017112245 |
+| 103 | core | findutils | 4.9.0 | 20241017114404 |
+| 104 | core | firejail | 0.9.72 | 20241017164310 |
+| 105 | core | fixesproto | 5.0 | 20241017135553 |
+| 106 | core | flex | 2.6.4 | 20241017114534 |
+| 107 | core | flex-stage0 | 2.6.4 | 20241017090424 |
+| 108 | core | flex-stage1 | 2.6.4 | 20241017094848 |
+| 109 | core | fontconfig | 2.15.0 | 20241017145137 |
+| 110 | core | freetype | 2.13.2 | 20241017144546 |
+| 111 | core | fribidi | 1.0.15 | 20241017161945 |
+| 112 | core | gawk | 5.3.0 | 20241017114217 |
+| 113 | core | gcc | 12.2.0 | 20241017105633 |
+| 114 | core | gcc-base | 12.2.0 | 20241017100502 |
+| 115 | core | gcc-libs | 12.2.0 | 20241017104024 |
+| 116 | core | gcc-libs-stage1 | 12.2.0 | 20241017094659 |
+| 117 | core | gcc-stage0 | 12.2.0 | 20241017085040 |
+| 118 | core | gcc-stage1 | 12.2.0 | 20241017090607 |
+| 119 | core | gcc-stage1-with-glibc | 12.2.0 | 20241017094806 |
+| 120 | core | gdal | 3.6.2 | 20241018043746 |
+| 121 | core | gdbm | 1.23 | 20241017114628 |
+| 122 | core | gecode | 6.2.0 | 20241018045824 |
+| 123 | core | geos | 3.11.1 | 20241018034354 |
+| 124 | core | gettext | 0.21 | 20241017113803 |
+| 125 | core | ghc | 9.10.1 | 20241017163412 |
+| 126 | core | giflib | 5.2.1 | 20241017145607 |
+| 127 | core | git | 2.39.1 | 20241017134953 |
+| 128 | core | glib | 2.81.0 | 20241018004657 |
+| 129 | core | glibc | 2.36 | 20241017094131 |
+| 130 | core | glibc-stage0 | 2.36 | 20241017084524 |
+| 131 | core | gmp | 6.2.1 | 20241017111320 |
+| 132 | core | gmp-stage0 | 6.2.1 | 20241017085637 |
+| 133 | core | gmp-stage1 | 6.2.1 | 20241017095635 |
+| 134 | core | gnupg | 2.4.5 | 20241017155543 |
+| 135 | core | gnutls | 3.7.11 | 20241017153407 |
+| 136 | core | go1_19 | 1.19.13 | 20241017134052 |
+| 137 | core | go1_21 | 1.21.9 | 20241017134517 |
+| 138 | core | go1_22 | 1.22.5 | 20241018035912 |
+| 139 | core | go-stage0 | 1.4.3 | 20241017133918 |
+| 140 | core | gperf | 3.1 | 20241017145040 |
+| 141 | core | gpgme | 1.23.2 | 20241017155801 |
+| 142 | core | grep | 3.8 | 20241017113254 |
+| 143 | core | groff | 1.22.4 | 20241018005250 |
+| 144 | core | grpcurl | 1.9.1 | 20241017164430 |
+| 145 | core | guile | 2.2.7 | 20241018021411 |
+| 146 | core | gzip | 1.13 | 20241017113655 |
+| 147 | core | hab-cc-wrapper | 1.0.0 | 20241017071227 |
+| 148 | core | hab-ld-wrapper | 1.0.0 | 20241017065142 |
+| 149 | core | happy | 1.20.1.1 | 20241017164114 |
+| 150 | core | haproxy | 2.8.5 | 20241018031710 |
+| 151 | core | harfbuzz | 9.0.0 | 20241018004909 |
+| 152 | core | iana-etc | 20220922 | 20241017105554 |
+| 153 | core | icu | 72.1 | 20241017131447 |
+| 154 | core | inetutils | 2.4 | 20241017133738 |
+| 155 | core | inputproto | 2.3.2 | 20241017161338 |
+| 156 | core | iproute2 | 6.9.0 | 20241018043338 |
+| 157 | core | iptables | 1.8.10 | 20241018043236 |
+| 158 | core | isl | 0.25 | 20241018050849 |
+| 159 | core | isl-stage0 | 0.25 | 20241017085815 |
+| 160 | core | isl-stage1 | 0.25 | 20241017095821 |
+| 161 | core | jbigkit | 2.1 | 20241017132918 |
+| 162 | core | jq-static | 1.7.1 | 20241018005910 |
+| 163 | core | json-c | 0.16 | 20241017160419 |
+| 164 | core | jsoncpp | 1.9.5 | 20241017131300 |
+| 165 | core | kbproto | 1.0.7 | 20241017161413 |
+| 166 | core | krb5 | 1.21.2 | 20241018020903 |
+| 167 | core | lcms2 | 2.16 | 20241017133121 |
+| 168 | core | lerc | 4.0.0 | 20241017132753 |
+| 169 | core | less | 643 | 20241017113607 |
+| 170 | core | libaio | 0.3.113 | 20241018005502 |
+| 171 | core | libarchive | 3.7.4 | 20241017132032 |
+| 172 | core | libassuan | 2.5.5 | 20241017154420 |
+| 173 | core | libatomic_ops | 7.8.2 | 20241017142240 |
+| 174 | core | libb2 | 0.98.1 | 20241017131349 |
+| 175 | core | libbsd | 0.11.7 | 20241017123959 |
+| 176 | core | libcap | 2.66 | 20241017111704 |
+| 177 | core | libcap-stage1 | 2.66 | 20241017110541 |
+| 178 | core | libdeflate | 1.15 | 20241017132833 |
+| 179 | core | libdrm | 2.4.122 | 20241017152911 |
+| 180 | core | libedit | 20230828-3.1 | 20241018010239 |
+| 181 | core | libevent | 2.1.12 | 20241017155117 |
+| 182 | core | libffi | 3.4.4 | 20241017125515 |
+| 183 | core | libgcrypt | 1.10.3 | 20241017155401 |
+| 184 | core | libgeotiff | 1.7.1 | 20241018041154 |
+| 185 | core | libgpg-error | 1.46 | 20241017154325 |
+| 186 | core | libice | 1.1.1 | 20241017144754 |
+| 187 | core | libiconv | 1.17 | 20241018004256 |
+| 188 | core | libidn2 | 2.3.3 | 20241017122705 |
+| 189 | core | libjpeg-turbo | 2.1.4 | 20241017132658 |
+| 190 | core | libksba | 1.6.7 | 20241017155257 |
+| 191 | core | libmd | 1.0.4 | 20241017123910 |
+| 192 | core | libmpc | 1.2.1 | 20241017124734 |
+| 193 | core | libmpc-stage0 | 1.2.1 | 20241017090123 |
+| 194 | core | libmpc-stage1 | 1.2.1 | 20241017100143 |
+| 195 | core | libnl | 3.2.25 | 20241018032036 |
+| 196 | core | libossp-uuid | 1.6.2 | 20241017142439 |
+| 197 | core | libpcap | 1.10.4 | 20241017162701 |
+| 198 | core | libpciaccess | 0.17 | 20241018021221 |
+| 199 | core | libpcre2 | 10.42 | 20241017113514 |
+| 200 | core | libpng | 1.6.37 | 20241017133215 |
+| 201 | core | libpsl | 0.21.1 | 20241017122817 |
+| 202 | core | libpthread-stubs | 0.4 | 20241017161127 |
+| 203 | core | librhash | 1.4.3 | 20241017132307 |
+| 204 | core | libseccomp | 2.5.4 | 20241017155936 |
+| 205 | core | libsm | 1.2.4 | 20241018043152 |
+| 206 | core | libsodium | 1.0.18 | 20241017162753 |
+| 207 | core | libtasn1 | 4.19.0 | 20241017153116 |
+| 208 | core | libtiff | 4.5.0 | 20241017133006 |
+| 209 | core | libtool | 2.4.7 | 20241017123322 |
+| 210 | core | libunistring | 1.0 | 20241017121901 |
+| 211 | core | libunwind | 1.6.2 | 20241018004517 |
+| 212 | core | libuv | 1.44.2 | 20241017132227 |
+| 213 | core | libwebp | 1.2.4 | 20241017152952 |
+| 214 | core | libxau | 1.0.9 | 20241017155209 |
+| 215 | core | libxcb | 1.14 | 20241017161209 |
+| 216 | core | libxdmcp | 1.1.3 | 20241017161049 |
+| 217 | core | libxext | 1.3.4 | 20241018005059 |
+| 218 | core | libxfixes | 5.0.3 | 20241018024653 |
+| 219 | core | libxi | 1.7.10 | 20241018024737 |
+| 220 | core | libxml2 | 2.11.5 | 20241017131712 |
+| 221 | core | libxrender | 0.9.10 | 20241017161750 |
+| 222 | core | libxslt | 1.1.34 | 20241017140159 |
+| 223 | core | libxtst | 1.2.4 | 20241018035010 |
+| 224 | core | libyaml | 0.2.5 | 20241017135627 |
+| 225 | core | linux-headers | 5.19.8 | 20241017082755 |
+| 226 | core | linux-headers-musl | 4.19.88-2 | 20241017160957 |
+| 227 | core | llvm | 18.1.6 | 20241018012248 |
+| 228 | core | local-lib | 2.000029 | 20241017160259 |
+| 229 | core | lsof | 4.99.3 | 20241018032208 |
+| 230 | core | lttng-ust | 2.13.8 | 20241018031540 |
+| 231 | core | lua | 5.4.6 | 20241018025105 |
+| 232 | core | lz4 | 1.9.4 | 20241017131823 |
+| 233 | core | lzip | 1.23 | 20241017120817 |
+| 234 | core | lzo | 2.10 | 20241017120900 |
+| 235 | core | lzop | 1.04 | 20241017120956 |
+| 236 | core | m4 | 1.4.19 | 20241017110128 |
+| 237 | core | m4-stage0 | 1.4.19 | 20241017085527 |
+| 238 | core | make | 4.4.1 | 20241017114721 |
+| 239 | core | maven | 3.9.7 | 20241018050436 |
+| 240 | core | maven-stage1 | 3.9.7 | 20241018034836 |
+| 241 | core | memcached | 1.6.18 | 20241018035228 |
+| 242 | core | meson | 1.5.0 | 20241017143847 |
+| 243 | core | mg | 20230501 | 20241017124052 |
+| 244 | core | minio | 2023-11-01T01-57-10Z | 20241018025633 |
+| 245 | core | mongodb | 7.0.14 | 20241018034209 |
+| 246 | core | mpfr | 4.1.0 | 20241017111518 |
+| 247 | core | mpfr-stage0 | 4.1.0 | 20241017090018 |
+| 248 | core | mpfr-stage1 | 4.1.0 | 20241017100031 |
+| 249 | core | musl | 1.2.5 | 20241017143945 |
+| 250 | core | mysql-client | 8.4.0 | 20241018042230 |
+| 251 | core | nasm | 2.16.03 | 20241017153655 |
+| 252 | core | native-busybox-static | 1.36.1 | 20241017082619 |
+| 253 | core | native-cross-binutils | 2.39 | 20241017065222 |
+| 254 | core | native-cross-gcc | 12.2.0 | 20241017071309 |
+| 255 | core | native-cross-gcc-base | 12.2.0 | 20241017065855 |
+| 256 | core | native-file | 5.42 | 20241017075915 |
+| 257 | core | native-gmp | 6.2.1 | 20241017065526 |
+| 258 | core | native-isl | 0.25 | 20241017065634 |
+| 259 | core | native-libmpc | 1.2.1 | 20241017065821 |
+| 260 | core | native-mpfr | 4.1.0 | 20241017065739 |
+| 261 | core | native-patchelf | 0.18.0 | 20241017080341 |
+| 262 | core | native-rust | 1.79.0 | 20241017064842 |
+| 263 | core | ncurses | 6.4 | 20241017105827 |
+| 264 | core | ncurses-stage1 | 6.4 | 20241017112908 |
+| 265 | core | netcat | 0.7.1 | 20241018034127 |
+| 266 | core | netcat-openbsd | 1.226 | 20241018034621 |
+| 267 | core | nettle | 3.9 | 20241017152749 |
+| 268 | core | net-tools | 2.10 | 20241017164546 |
+| 269 | core | nghttp2 | 1.51.0 | 20241017130939 |
+| 270 | core | nginx | 1.25.3 | 20241018020551 |
+| 271 | core | ninja | 1.12.1 | 20241017144840 |
+| 272 | core | node | 18.20.4 | 20241017145745 |
+| 273 | core | npth | 1.7 | 20241017144501 |
+| 274 | core | nspr | 4.35 | 20241018005417 |
+| 275 | core | nss | 3.102 | 20241018010336 |
+| 276 | core | nss-myhostname | 0.3 | 20241017135707 |
+| 277 | core | numactl | 2.0.18 | 20241018031441 |
+| 278 | core | oniguruma | 6.9.8 | 20241018005817 |
+| 279 | core | openjpeg | 2.5.2 | 20241017133348 |
+| 280 | core | openldap | 2.6.8 | 20241018044712 |
+| 281 | core | openssh | 9.8p1 | 20241017134753 |
+| 282 | core | openssl | 3.0.9 | 20241017121505 |
+| 283 | core | openssl-musl | 3.0.9 | 20241017144105 |
+| 284 | core | p11-kit | 0.25.5 | 20241017153249 |
+| 285 | core | pango | 1.54.0 | 20241018045520 |
+| 286 | core | parallel | 20221222 | 20241017123727 |
+| 287 | core | patch | 2.7.6 | 20241017121041 |
+| 288 | core | patchelf | 0.18.0 | 20241017133303 |
+| 289 | core | pcre2 | 10.42 | 20241017113156 |
+| 290 | core | perl | 5.36.0 | 20241017114910 |
+| 291 | core | pixman | 0.43.4 | 20241017144950 |
+| 292 | core | pkg-config | 0.29.2 | 20241017105716 |
+| 293 | core | popt | 1.19 | 20241018012135 |
+| 294 | core | postgis3 | 3.3.2 | 20241018044321 |
+| 295 | core | postgresql13 | 13.14 | 20241018035541 |
+| 296 | core | postgresql13-client | 13.14 | 20241017162050 |
+| 297 | core | postgresql14 | 14.11 | 20241017143002 |
+| 298 | core | postgresql14-client | 14.11 | 20241018035358 |
+| 299 | core | postgresql15 | 15.6 | 20241017142552 |
+| 300 | core | postgresql15-client | 15.6 | 20241018043548 |
+| 301 | core | postgresql-with-ext15 | 15.6 | 20241018044520 |
+| 302 | core | powershell | 7.4.3 | 20241018031929 |
+| 303 | core | procps-ng | 4.0.4 | 20241017114811 |
+| 304 | core | proj | 9.1.1 | 20241018030308 |
+| 305 | core | prometheus | 2.53.2 | 20241017152357 |
+| 306 | core | protobuf | 21.12 | 20241017115236 |
+| 307 | core | protobuf-c | 1.4.1 | 20241018004140 |
+| 308 | core | protobuf-cpp | 3.21.12 | 20241018003140 |
+| 309 | core | protobuf-rust | 1.7.5 | 20241017133617 |
+| 310 | core | psmisc | 23.5 | 20241018024606 |
+| 311 | core | python | 3.10.8 | 20241017125721 |
+| 312 | core | python2-stage1 | 2.7.18 | 20241017140258 |
+| 313 | core | raml2html | 7.8.0 | 20241017161828 |
+| 314 | core | re2c | 3.0 | 20241017142828 |
+| 315 | core | readline | 8.2 | 20241017110036 |
+| 316 | core | readline-stage1 | 8.2 | 20241017113107 |
+| 317 | core | recordproto | 1.14.2 | 20241018010024 |
+| 318 | core | redis | 7.0.8 | 20241017160824 |
+| 319 | core | renderproto | 0.11.1 | 20241017154247 |
+| 320 | core | rpm | 4.18.2 | 20241018025209 |
+| 321 | core | rsync | 3.2.7 | 20241018005712 |
+| 322 | core | ruby3_1 | 3.1.6 | 20241017135756 |
+| 323 | core | ruby3_3 | 3.3.0 | 20241018002804 |
+| 324 | core | ruby3_4 | 3.4.0 | 20241017143227 |
+| 325 | core | ruby-stage1 | 3.2.1 | 20241017143604 |
+| 326 | core | runc | 1.1.14 | 20241017160615 |
+| 327 | core | runit | 2.1.2 | 20241018035314 |
+| 328 | core | rust | 1.79.0 | 20241017115515 |
+| 329 | core | scaffolding-base | 0.1.0 | 20241017145628 |
+| 330 | core | scaffolding-go | 0.2.0 | 20241017160526 |
+| 331 | core | sccache | 0.8.1 | 20241018040537 |
+| 332 | core | scons | 4.6.0 | 20241018005145 |
+| 333 | core | sed | 4.9 | 20241017112756 |
+| 334 | core | shadow | 4.12.3 | 20241017111040 |
+| 335 | core | shellcheck | 0.10.0 | 20241018051136 |
+| 336 | core | sqitch | 1.4.1 | 20241017162311 |
+| 337 | core | sqlite | 3.45.3 | 20241017125615 |
+| 338 | core | strace | 6.0 | 20241018045611 |
+| 339 | core | sudo | 1.9.15p5 | 20241017135353 |
+| 340 | core | tar | 1.35 | 20241017121251 |
+| 341 | core | tcl | 8.6.12 | 20241017112337 |
+| 342 | core | tcl-stage1 | 8.6.12 | 20241017104426 |
+| 343 | core | terraform | 1.7.3 | 20241017140052 |
+| 344 | core | texinfo | 7.0.1 | 20241017123603 |
+| 345 | core | toml-cli | 0.2.3 | 20241017120659 |
+| 346 | core | tzdata | 2024a | 20241017104115 |
+| 347 | core | unzip | 6.0 | 20241017121423 |
+| 348 | core | userspace-rcu | 0.14.0 | 20241017142320 |
+| 349 | core | util-linux | 2.38.1 | 20241017123049 |
+| 350 | core | util-macros | 1.19.3 | 20241017135520 |
+| 351 | core | valgrind | 3.18.1 | 20241017122152 |
+| 352 | core | vault | 1.17.3 | 20241018024425 |
+| 353 | core | vim | 9.1.0318 | 20241017124141 |
+| 354 | core | wget | 1.24.5 | 20241017122922 |
+| 355 | core | wget-static | 1.24.5 | 20241018010111 |
+| 356 | core | which | 2.21 | 20241017152252 |
+| 357 | core | xcb-proto | 1.14 | 20241017142203 |
+| 358 | core | xextproto | 7.3.0 | 20241017145246 |
+| 359 | core | xlib | 1.8.7 | 20241017161507 |
+| 360 | core | xproto | 7.0.31 | 20241017144640 |
+| 361 | core | xtrans | 1.4.0 | 20241017144716 |
+| 362 | core | xxhash | 0.8.1 | 20241017133703 |
+| 363 | core | xz | 5.2.6 | 20241017112102 |
+| 364 | core | xz-stage0 | 5.2.6 | 20241017090507 |
+| 365 | core | yarn | 1.22.22 | 20241017152214 |
+| 366 | core | zeromq | 4.3.4 | 20241017163014 |
+| 367 | core | zlib | 1.3.1 | 20241017112207 |
+| 368 | core | zlib-musl | 1.3.1 | 20241017144029 |
+| 369 | core | zlib-stage0 | 1.3.1 | 20241017085109 |
+| 370 | core | zlib-stage1 | 1.3.1 | 20241017094938 |
+| 371 | core | zstd | 1.5.2 | 20241017121149 |
+| 372 | core | zstd-stage0 | 1.5.2 | 20241017090203 |
+| 373 | core | zstd-stage1 | 1.5.2 | 20241017100230 |
+
+### Arch 64 architecture
+
+| S.No | Origin | Package Name | version | Ident |
+|------|--------|---------------------------|----------------------|----------------|
+| 1 | core | acl | 2.3.1 | 20240805113626 |
+| 2 | core | acl-stage1 | 2.3.1 | 20240805113101 |
+| 3 | core | attr | 2.5.1 | 20240805113544 |
+| 4 | core | attr-stage1 | 2.5.1 | 20240805113023 |
+| 5 | core | autoconf | 2.71 | 20240805132651 |
+| 6 | core | automake | 1.16.5 | 20240805132740 |
+| 7 | core | aws-cli | 2.15.38 | 20240805174030 |
+| 8 | core | bash | 5.2.21 | 20240805115150 |
+| 9 | core | bash-static | 5.2.21 | 20240805174344 |
+| 10 | core | bats | 1.8.2 | 20240805133058 |
+| 11 | core | bc | 6.0.4 | 20240805181416 |
+| 12 | core | binutils | 2.39 | 20240805112112 |
+| 13 | core | binutils-stage0 | 2.39 | 20240805085007 |
+| 14 | core | binutils-stage1 | 2.39 | 20240805100354 |
+| 15 | core | bison | 3.8.2 | 20240805115013 |
+| 16 | core | build-tools-bash-static | 5.2.21 | 20240805074004 |
+| 17 | core | build-tools-binutils | 2.39 | 20240805065355 |
+| 18 | core | build-tools-bison | 3.8.2 | 20240805082857 |
+| 19 | core | build-tools-cacerts | 2023.12.12 | 20240805075900 |
+| 20 | core | build-tools-coreutils | 9.4 | 20240805064312 |
+| 21 | core | build-tools-diffutils | 3.8 | 20240805074758 |
+| 22 | core | build-tools-file | 5.42 | 20240805074518 |
+| 23 | core | build-tools-findutils | 4.9.0 | 20240805074606 |
+| 24 | core | build-tools-gawk | 5.3.0 | 20240805064717 |
+| 25 | core | build-tools-gcc | 12.2.0 | 20240805070956 |
+| 26 | core | build-tools-gcc-libs | 12.2.0 | 20240805075049 |
+| 27 | core | build-tools-gettext | 0.21 | 20240805082353 |
+| 28 | core | build-tools-glibc | 2.36 | 20240805063011 |
+| 29 | core | build-tools-gmp | 6.2.1 | 20240805070040 |
+| 30 | core | build-tools-grep | 3.8 | 20240805064838 |
+| 31 | core | build-tools-gzip | 1.13 | 20240805074920 |
+| 32 | core | build-tools-isl | 0.25 | 20240805070309 |
+| 33 | core | build-tools-libmpc | 1.2.1 | 20240805070649 |
+| 34 | core | build-tools-libstdcxx | 12.2.0 | 20240805063904 |
+| 35 | core | build-tools-linux-headers | 5.19.8 | 20240805061025 |
+| 36 | core | build-tools-m4 | 1.4.19 | 20240805082202 |
+| 37 | core | build-tools-make | 4.4.1 | 20240805065008 |
+| 38 | core | build-tools-mpfr | 4.1.0 | 20240805070510 |
+| 39 | core | build-tools-ncurses | 6.4 | 20240805081347 |
+| 40 | core | build-tools-openssl | 3.0.9 | 20240805080656 |
+| 41 | core | build-tools-patch | 2.7.6 | 20240805070733 |
+| 42 | core | build-tools-patchelf | 0.18.0 | 20240805075944 |
+| 43 | core | build-tools-perl | 5.36.0 | 20240805083733 |
+| 44 | core | build-tools-python | 3.10.8 | 20240805083030 |
+| 45 | core | build-tools-rust | 1.79.0 | 20240805080016 |
+| 46 | core | build-tools-sed | 4.9 | 20240805065054 |
+| 47 | core | build-tools-tar | 1.35 | 20240805065205 |
+| 48 | core | build-tools-texinfo | 6.8 | 20240805084108 |
+| 49 | core | build-tools-toml-cli | 0.2.3 | 20240805080524 |
+| 50 | core | build-tools-util-linux | 2.38.1 | 20240805111202 |
+| 51 | core | build-tools-wget | 1.21.3 | 20240805081155 |
+| 52 | core | build-tools-xz | 5.2.6 | 20240805070852 |
+| 53 | core | build-tools-zlib | 1.3.1 | 20240805075920 |
+| 54 | core | busybox-static | 1.36.1 | 20240805133911 |
+| 55 | core | bzip2 | 1.0.8 | 20240805115455 |
+| 56 | core | bzip2-stage0 | 1.0.8 | 20240805084930 |
+| 57 | core | cacerts | 2023.12.12 | 20240805121136 |
+| 58 | core | certstrap | 1.3.0 | 20240805175942 |
+| 59 | core | cmake | 3.25.1 | 20240805151847 |
+| 60 | core | cmake-stage1 | 3.25.1 | 20240805141834 |
+| 61 | core | coreutils | | 9.4 |
+| 62 | core | coreutils-stage1 | 9.4 | 20240805113229 |
+| 63 | core | cpanminus | 1.7047 | 20240805144815 |
+| 64 | core | cunit | 3.2.7 | 20240805142551 |
+| 65 | core | curl | 8.6.0 | 20240805144441 |
+| 66 | core | cyrus-sasl | 2.1.28 | 20240805170204 |
+| 67 | core | db | 5.3.28 | 20240805164500 |
+| 68 | core | dejagnu | 1.6.3 | 20240805123045 |
+| 69 | core | dejagnu-stage1 | 1.6.3 | 20240805112024 |
+| 70 | core | dex | 2.38.0 | 20240805164218 |
+| 71 | core | diffutils | 3.8 | 20240805114229 |
+| 72 | core | docker | 26.0.0 | 20240805175441 |
+| 73 | core | e2fsprogs | 1.46.4 | 20240805151337 |
+| 74 | core | erlang26 | 26.2.2 | 20240805183221 |
+| 75 | core | expat | 2.6.2 | 20240805135013 |
+| 76 | core | expect | 5.45.4 | 20240805121839 |
+| 77 | core | expect-stage1 | 5.45.4 | 20240805111931 |
+| 78 | core | file | 5.42 | 20240805121309 |
+| 79 | core | findutils | 4.9.0 | 20240805123121 |
+| 80 | core | firejail | 0.9.72 | 20240805191046 |
+| 81 | core | fixesproto | 5.0 | 20240805181156 |
+| 82 | core | flex | 2.6.4 | 20240805115529 |
+| 83 | core | flex-stage0 | 2.6.4 | 20240805090457 |
+| 84 | core | flex-stage1 | 2.6.4 | 20240805100225 |
+| 85 | core | gawk | 5.3.0 | 20240805122932 |
+| 86 | core | gcc | 12.2.0 | 20240805112950 |
+| 87 | core | gcc-base | 12.2.0 | 20240805102209 |
+| 88 | core | gcc-libs | 12.2.0 | 20240805111023 |
+| 89 | core | gcc-libs-stage1 | 12.2.0 | 20240805100043 |
+| 90 | core | gcc-stage0 | 12.2.0 | 20240805084836 |
+| 91 | core | gcc-stage1 | 12.2.0 | 20240805090638 |
+| 92 | core | gcc-stage1-with-glibc | 12.2.0 | 20240805100149 |
+| 93 | core | gdal | 3.6.2 | 20240805155316 |
+| 94 | core | gdbm | 1.23 | 20240805120425 |
+| 95 | core | gecode | 6.2.0 | 20240805134129 |
+| 96 | core | geos | 3.11.1 | 20240805152255 |
+| 97 | core | gettext | 0.21 | 20240805122351 |
+| 98 | core | giflib | 5.2.1 | 20240805152611 |
+| 99 | core | git | 2.39.1 | 20240805162253 |
+| 100 | core | glibc | 2.36 | 20240805095448 |
+| 101 | core | glibc-stage0 | 2.36 | 20240805084249 |
+| 102 | core | gmp | 6.2.1 | 20240805121927 |
+| 103 | core | gmp-stage0 | 6.2.1 | 20240805085535 |
+| 104 | core | gmp-stage1 | 6.2.1 | 20240805101212 |
+| 105 | core | go1_19 | 1.19.13 | 20240805163450 |
+| 106 | core | go1_21 | 1.21.9 | 20240805163913 |
+| 107 | core | go1_22 | 1.22.5 | 20240805184444 |
+| 108 | core | go-stage0 | 1.8.5 | 20240805163325 |
+| 109 | core | gperf | 3.1 | 20240805173914 |
+| 110 | core | grep | 3.8 | 20240805120029 |
+| 111 | core | groff | 1.22.4 | 20240805134644 |
+| 112 | core | grpcurl | 1.9.1 | 20240805182155 |
+| 113 | core | gzip | 1.13 | 20240805120323 |
+| 114 | core | hab-cc-wrapper | 1.0.0 | 20240805064215 |
+| 115 | core | hab-ld-wrapper | 1.0.0 | 20240805061606 |
+| 116 | core | haproxy | 2.8.5 | 20240805184754 |
+| 117 | core | iana-etc | 20220922 | 20240805112918 |
+| 118 | core | icu | 72.1 | 20240805145623 |
+| 119 | core | inetutils | 2.4 | 20240805163146 |
+| 120 | core | inputproto | 2.3.2 | 20240805150409 |
+| 121 | core | isl | 0.25 | 20240805183732 |
+| 122 | core | isl-stage0 | 0.25 | 20240805085734 |
+| 123 | core | isl-stage1 | 0.25 | 20240805101417 |
+| 124 | core | jbigkit | 2.1 | 20240805153004 |
+| 125 | core | jq-static | 1.7.1 | 20240805182314 |
+| 126 | core | json-c | 0.16 | 20240805152650 |
+| 127 | core | jsoncpp | 1.9.5 | 20240805151113 |
+| 128 | core | kbproto | 1.0.7 | 20240805150442 |
+| 129 | core | lerc | 4.0.0 | 20240805152739 |
+| 130 | core | less | 643 | 20240805120238 |
+| 131 | core | libarchive | 3.7.4 | 20240805151448 |
+| 132 | core | libassuan | 2.5.5 | 20240805184307 |
+| 133 | core | libb2 | 0.98.1 | 20240805151208 |
+| 134 | core | libbsd | 0.11.7 | 20240805133245 |
+| 135 | core | libcap | 2.66 | 20240805113833 |
+| 136 | core | libcap-stage1 | 2.66 | 20240805113146 |
+| 137 | core | libdeflate | 1.15 | 20240805152819 |
+| 138 | core | libedit | 20230828-3.1 | 20240805134920 |
+| 139 | core | libevent | 2.1.12 | 20240805174252 |
+| 140 | core | libffi | 3.4.4 | 20240805135102 |
+| 141 | core | libgeotiff | 1.7.1 | 20240805154936 |
+| 142 | core | libgpg-error | 1.46 | 20240805170305 |
+| 143 | core | libiconv | 1.17 | 20240805174145 |
+| 144 | core | libidn2 | 2.3.3 | 20240805131849 |
+| 145 | core | libjpeg-turbo | 2.1.4 | 20240805152909 |
+| 146 | core | libmd | 1.0.4 | 20240805133159 |
+| 147 | core | libmpc | 1.2.1 | 20240805134827 |
+| 148 | core | libmpc-stage0 | 1.2.1 | 20240805090116 |
+| 149 | core | libmpc-stage1 | 1.2.1 | 20240805101814 |
+| 150 | core | libossp-uuid | 1.6.2 | 20240805155935 |
+| 151 | core | libpcre2 | 10.42 | 20240805120146 |
+| 152 | core | libpng | 1.6.37 | 20240805155024 |
+| 153 | core | libpsl | 0.21.1 | 20240805132007 |
+| 154 | core | libpthread-stubs | 0.4 | 20240805145539 |
+| 155 | core | librhash | 1.4.3 | 20240805151809 |
+| 156 | core | libseccomp | 2.5.4 | 20240805173950 |
+| 157 | core | libsodium | 1.0.18 | 20240805181547 |
+| 158 | core | libtiff | 4.5.0 | 20240805153046 |
+| 159 | core | libtool | 2.4.7 | 20240805132600 |
+| 160 | core | libunistring | 1.0 | 20240805130749 |
+| 161 | core | libunwind | 1.6.2 | 20240805174528 |
+| 162 | core | libuv | 1.44.2 | 20240805151725 |
+| 163 | core | libwebp | 1.2.4 | 20240805155116 |
+| 164 | core | libxau | 1.0.9 | 20240805145420 |
+| 165 | core | libxcb | 1.14 | 20240805150216 |
+| 166 | core | libxdmcp | 1.1.3 | 20240805145500 |
+| 167 | core | libxext | 1.3.4 | 20240805151018 |
+| 168 | core | libxfixes | 5.0.3 | 20240805181230 |
+| 169 | core | libxi | 1.7.10 | 20240805181311 |
+| 170 | core | libxml2 | 2.10.3 | 20240805150018 |
+| 171 | core | libxrender | 0.9.10 | 20240805190550 |
+| 172 | core | libxslt | 1.1.34 | 20240805180717 |
+| 173 | core | libxtst | 1.2.4 | 20240805183655 |
+| 174 | core | libyaml | 0.2.5 | 20240805163005 |
+| 175 | core | linux-headers | 5.19.8 | 20240805082045 |
+| 176 | core | local-lib | 2.000029 | 20240805144743 |
+| 177 | core | lz4 | 1.9.4 | 20240805151257 |
+| 178 | core | lzip | 1.23 | 20240805125522 |
+| 179 | core | lzo | 2.10 | 20240805125600 |
+| 180 | core | lzop | 1.04 | 20240805125701 |
+| 181 | core | m4 | 1.4.19 | 20240805114841 |
+| 182 | core | m4-stage0 | 1.4.19 | 20240805085412 |
+| 183 | core | make | 4.4.1 | 20240805115335 |
+| 184 | core | memcached | 1.6.18 | 20240805190950 |
+| 185 | core | mg | 20230501 | 20240805133337 |
+| 186 | core | minio | 2023-11-01T01-57-10Z | 20240805182635 |
+| 187 | core | mpfr | 4.1.0 | 20240805122158 |
+| 188 | core | mpfr-stage0 | 4.1.0 | 20240805090003 |
+| 189 | core | mpfr-stage1 | 4.1.0 | 20240805101653 |
+| 190 | core | musl | 1.2.5 | 20240805184121 |
+| 191 | core | native-busybox-static | 1.36.1 | 20240805081911 |
+| 192 | core | native-cross-binutils | 2.39 | 20240805061649 |
+| 193 | core | native-cross-gcc | 12.2.0 | 20240805064253 |
+| 194 | core | native-cross-gcc-base | 12.2.0 | 20240805062556 |
+| 195 | core | native-file | 5.42 | 20240805074442 |
+| 196 | core | native-gmp | 6.2.1 | 20240805062127 |
+| 197 | core | native-isl | 0.25 | 20240805062253 |
+| 198 | core | native-libmpc | 1.2.1 | 20240805062516 |
+| 199 | core | native-mpfr | 4.1.0 | 20240805062421 |
+| 200 | core | native-patchelf | 0.18.0 | 20240805075011 |
+| 201 | core | native-rust | 1.79.0 | 20240805061149 |
+| 202 | core | ncurses | 6.4 | 20240805114510 |
+| 203 | core | ncurses-stage1 | 6.4 | 20240805115618 |
+| 204 | core | netcat-openbsd | 1.226 | 20240805174649 |
+| 205 | core | net-tools | 2.10 | 20240805184352 |
+| 206 | core | nghttp2 | 1.51.0 | 20240805144344 |
+| 207 | core | nginx | 1.25.3 | 20240805170022 |
+| 208 | core | ninja | 1.11.1 | 20240805164814 |
+| 209 | core | node | 18.20.4 | 20240805170543 |
+| 210 | core | nss-myhostname | 0.3 | 20240805164855 |
+| 211 | core | oniguruma | 6.9.8 | 20240805180024 |
+| 212 | core | openssh | 9.8p1 | 20240805162035 |
+| 213 | core | openssl | 3.0.9 | 20240805130249 |
+| 214 | core | parallel | 20221222 | 20240805133012 |
+| 215 | core | patch | 2.7.6 | 20240805125744 |
+| 216 | core | patchelf | 0.18.0 | 20240805161756 |
+| 217 | core | pcre2 | 10.42 | 20240805115930 |
+| 218 | core | perl | 5.36.0 | 20240805120739 |
+| 219 | core | pkg-config | 0.29.2 | 20240805114351 |
+| 220 | core | postgis3 | 3.3.2 | 20240805162534 |
+| 221 | core | postgresql13 | 13.14 | 20240805190644 |
+| 222 | core | postgresql13-client | 13.14 | 20240805191208 |
+| 223 | core | postgresql14 | 14.11 | 20240805180414 |
+| 224 | core | postgresql14-client | 14.11 | 20240805190342 |
+| 225 | core | postgresql15 | 15.6 | 20240805160031 |
+| 226 | core | postgresql15-client | 15.6 | 20240805182434 |
+| 227 | core | postgresql-with-ext15 | 15.6 | 20240805162800 |
+| 228 | core | procps-ng | 4.0.4 | 20240805120636 |
+| 229 | core | proj | 9.1.1 | 20240805153231 |
+| 230 | core | protobuf | 21.12 | 20240805123308 |
+| 231 | core | protobuf-c | 1.4.1 | 20240805161639 |
+| 232 | core | protobuf-cpp | 3.21.12 | 20240805160333 |
+| 233 | core | protobuf-rust | 1.7.5 | 20240805185225 |
+| 234 | core | psmisc | 23.5 | 20240805181501 |
+| 235 | core | python | 3.10.8 | 20240805142625 |
+| 236 | core | python2-stage1 | 2.7.18 | 20240805135312 |
+| 237 | core | raml2html | 7.8.0 | 20240805175815 |
+| 238 | core | re2c | 3.0 | 20240805164701 |
+| 239 | core | readline | 8.2 | 20240805114749 |
+| 240 | core | readline-stage1 | 8.2 | 20240805115842 |
+| 241 | core | recordproto | 1.14.2 | 20240805183617 |
+| 242 | core | redis | 7.0.8 | 20240805180129 |
+| 243 | core | renderproto | 0.11.1 | 20240805180328 |
+| 244 | core | rsync | 3.2.7 | 20240805161917 |
+| 245 | core | ruby3_1 | 3.1.3 | 20240805191413 |
+| 246 | core | ruby3_3 | 3.3.0 | 20240805182752 |
+| 247 | core | ruby-stage1 | 3.2.1 | 20240805180822 |
+| 248 | core | runit | 2.1.2 | 20240805170405 |
+| 249 | core | rust | 1.79.0 | 20240805123619 |
+| 250 | core | sccache | 0.8.1 | 20240805165058 |
+| 251 | core | sed | 4.9 | 20240805120517 |
+| 252 | core | shadow | 4.12.3 | 20240805113716 |
+| 253 | core | sqitch | 1.4.1 | 20240805144853 |
+| 254 | core | sqlite | 3.45.3 | 20240805135148 |
+| 255 | core | strace | 6.0 | 20240805175555 |
+| 256 | core | tar | 1.35 | 20240805130024 |
+| 257 | core | tcl | 8.6.12 | 20240805121403 |
+| 258 | core | tcl-stage1 | 8.6.12 | 20240805111447 |
+| 259 | core | terraform | 1.7.3 | 20240805163036 |
+| 260 | core | texinfo | 7.0.1 | 20240805132831 |
+| 261 | core | toml-cli | 0.2.3 | 20240805125341 |
+| 262 | core | tzdata | 2024a | 20240805111115 |
+| 263 | core | unzip | 6.0 | 20240805130211 |
+| 264 | core | util-linux | 2.38.1 | 20240805132238 |
+| 265 | core | util-macros | 1.19.3 | 20240805145315 |
+| 266 | core | valgrind | 3.18.1 | 20240805131132 |
+| 267 | core | vim | 9.1.0318 | 20240805133421 |
+| 268 | core | wget | 1.21.3 | 20240805132101 |
+| 269 | core | which | 2.21 | 20240805162435 |
+| 270 | core | xcb-proto | 1.14 | 20240805150138 |
+| 271 | core | xextproto | 7.3.0 | 20240805150516 |
+| 272 | core | xlib | 1.8.7 | 20240805150642 |
+| 273 | core | xproto | 7.0.31 | 20240805145344 |
+| 274 | core | xtrans | 1.4.0 | 20240805150550 |
+| 275 | core | xxhash | 0.8.1 | 20240805161835 |
+| 276 | core | xz | 5.2.6 | 20240805121206 |
+| 277 | core | xz-stage0 | 5.2.6 | 20240805090539 |
+| 278 | core | zeromq | 4.3.4 | 20240805181815 |
+| 279 | core | zlib | 1.3.1 | 20240805115422 |
+| 280 | core | zlib-stage0 | 1.3.1 | 20240805084859 |
+| 281 | core | zlib-stage1 | 1.3.1 | 20240805100312 |
+| 282 | core | zstd | 1.5.2 | 20240805125858 |
+| 283 | core | zstd-stage0 | 1.5.2 | 20240805090155 |
+| 284 | core | zstd-stage1 | 1.5.2 | 20240805101858 |
+| 285 | core | pango | 1.54.0 | 20241018045520 |
+| 286 | core | pixman | 0.43.4 | 20241017144950 |
+| 287 | core | popt | 1.19 | 20241018012135 |
+| 288 | core | powershell | 7.4.3 | 20241018031929 |
+| 289 | core | prometheus | 2.53.2 | 20241017152357 |
+| 290 | core | rpm | 4.18.2 | 20241018025209 |
+| 291 | core | runc | 1.1.14 | 20241017160615 |
+| 292 | core | scaffolding-base | 0.1.0 | 20241017145628 |
+| 293 | core | scaffolding-go | 0.2.0 | 20241017160526 |
+| 294 | core | scons | 4.6.0 | 20241018005145 |
+| 295 | core | shellcheck | 0.10.0 | 20241018051136 |
+| 296 | core | userspace-rcu | 0.14.0 | 20241017142320 |
+| 297 | core | wget-static | 1.24.5 | 20241018010111 |
+| 298 | core | yarn | 1.22.22 | 20241017152214 |
+| 299 | core | zlib-musl | 1.3.1 | 20241017144029 |
+| 300 | core | buildah | 1.37.3 | 20240927105019 |
+| 301 | core | gpgme | 1.23.2 | 20240927104839 |
+| 302 | core | gnupg | 2.4.5 | 20240927104603 |
+| 303 | core | libgcrypt | 1.10.3 | 20240927104437 |
+| 304 | core | npth | 1.7 | 20240927104407 |
+| 305 | core | libksba | 1.6.7 | 20240927104035 |
+
+### Windows platform
+
+| S.No | Origin | Package Name | Version | Ident |
+|------|--------|--------------------------|-------------|----------------|
+| 1 | core | 7zip | 24.06 | 20240809045309 |
+| 2 | core | asciinema | 2.4.0 | 20240809055337 |
+| 3 | core | aws-cli | 1.33.39 | 20240809071335 |
+| 4 | core | buildkite-agent | 3.73.1 | 20240809080020 |
+| 5 | core | buildkite-cli | 2.0.0 | 20240809091729 |
+| 6 | core | bzip2 | 1.0.8 | 20240809071025 |
+| 7 | core | cabal-install | 3.10.3.0 | 20240809075605 |
+| 8 | core | cacerts | 2024.07.02 | 20240809094209 |
+| 9 | core | cmake | 3.29.3 | 20240809055507 |
+| 10 | core | concourse | 7.11.2 | 20240809100218 |
+| 11 | core | corretto11 | 11.0.23.9.1 | 20240809080413 |
+| 12 | core | docker | 26.1.4 | 20240809100452 |
+| 13 | core | docker-credential-helper | 0.8.2 | 20240809054342 |
+| 14 | core | dotnet-core-sdk | 8.0.303 | 20240809091824 |
+| 15 | core | ghc | 9.10.1 | 20240809071855 |
+| 16 | core | git | 2.45.1 | 20240809051854 |
+| 17 | core | go1_22 | 1.22.4 | 20240809054403 |
+| 18 | core | innounp | 0.5 | 20240809093415 |
+| 19 | core | jq-static | 1.7.1 | 20240809080001 |
+| 20 | core | lessmsi | 2.0.1 | 20240809042911 |
+| 21 | core | libarchive | 3.7.4 | 20240809084847 |
+| 22 | core | libsodium | 1.0.20 | 20240809093353 |
+| 23 | core | maven | 3.9.7 | 20240809101508 |
+| 24 | core | nasm | 2.16.03 | 20240809075941 |
+| 25 | core | nginx | 1.26.0 | 20240809101606 |
+| 26 | core | node | 20.13.1 | 20240809054132 |
+| 27 | core | nuget | 6.10.0 | 20240809052336 |
+| 28 | core | openssl | 3.3.1 | 20240809080654 |
+| 29 | core | packer | 1.11.0 | 20240809100138 |
+| 30 | core | perl | 5.41.2 | 20240809052614 |
+| 31 | core | pester | 5.5.0 | 20240809100314 |
+| 32 | core | postgresql15-client | 15.6 | 20240809092951 |
+| 33 | core | powershell | 7.5.0 | 20240809100552 |
+| 34 | core | protobuf | 3.27.3 | 20240809094228 |
+| 35 | core | ps-lock | 0.1.1 | 20240809055451 |
+| 36 | core | psscriptanalyzer | 1.22.0 | 20240809100351 |
+| 37 | core | python | 3.12.0 | 20240809052402 |
+| 38 | core | raml2html | 7.8.0 | 20240809100914 |
+| 39 | core | rust | 1.79.0 | 20240809060126 |
+| 40 | core | shellcheck | 0.10.0 | 20240809080056 |
+| 41 | core | visual-build-tools-2022 | 17.10.4 | 20240809045337 |
+| 42 | core | visual-cpp-redist-2022 | 14.40.33810 | 20240809051437 |
+| 43 | core | windows-11-sdk | 10.0.22621 | 20240809042940 |
+| 44 | core | wix | 3.14.1 | 20240809051319 |
+| 45 | core | xz | 5.2.9 | 20240809051834 |
+| 46 | core | yarn | 1.22.22 | 20240809093313 |
+| 47 | core | zeromq | 4.3.5 | 20240809093437 |
+| 48 | core | zlib | 1.3.1 | 20240809051508 |
diff --git a/content/release_notes_inspec.md b/content/release_notes_inspec.md
index 279adc9d14..7af5e4d213 100644
--- a/content/release_notes_inspec.md
+++ b/content/release_notes_inspec.md
@@ -12,5 +12,5 @@ toc_layout = "release_notes_toc"
title = "Chef InSpec"
identifier = "release_notes/release_notes_inspec.md Chef InSpec"
parent = "release_notes"
- weight = 70
+ weight = 80
+++
\ No newline at end of file
diff --git a/content/release_notes_local_license_service.md b/content/release_notes_local_license_service.md
index 25da04a759..b95c09f19d 100644
--- a/content/release_notes_local_license_service.md
+++ b/content/release_notes_local_license_service.md
@@ -8,7 +8,7 @@ product = []
title = "Chef Local License Service"
identifier = "release_notes/Chef Local License Service"
parent = "release_notes"
- weight = 80
+ weight = 90
+++
Chef Local License Service provides license keys to commercially licensed Chef software in an online or air-gapped environment.
diff --git a/content/release_notes_manage.md b/content/release_notes_manage.md
index 5a32314180..1e13619e51 100644
--- a/content/release_notes_manage.md
+++ b/content/release_notes_manage.md
@@ -13,7 +13,7 @@ toc_layout = "release_notes_toc"
title = "Chef Manage"
identifier = "release_notes/release_notes_manage.md Chef Manage"
parent = "release_notes"
- weight = 90
+ weight = 95
+++
Chef Manage provides a web-based user interface that manages Chef Infra nodes and other policy objects, such as data bags and roles, on the instance of Chef Infra Server that it's installed on.
diff --git a/content/release_notes_server.md b/content/release_notes_server.md
index 72416decbd..6a8118b14c 100644
--- a/content/release_notes_server.md
+++ b/content/release_notes_server.md
@@ -12,5 +12,5 @@ toc_layout = "release_notes_toc"
title = "Chef Infra Server"
identifier = "release_notes/release_notes_server.md Chef Infra Server"
parent = "release_notes"
- weight = 60
+ weight = 70
+++
diff --git a/content/resource.md b/content/resource.md
index 2f0e806c86..bf2cea723f 100644
--- a/content/resource.md
+++ b/content/resource.md
@@ -35,7 +35,7 @@ resources, for example those used to send notifications to other
resources and guards that help ensure that some resources are
idempotent.
-For example, a resource that is used to install a tar.gz package for
+For example, a resource that's used to install a tar.gz package for
version 1.16.1 may look something like this:
```ruby
@@ -48,7 +48,7 @@ end
All actions have a default value. Only non-default behaviors of actions
and properties need to be specified. For example, the **package**
resource's default action is `:install` and the name of the package
-defaults to the `name` of the resource. Therefore, it is possible to
+defaults to the `name` of the resource. Therefore, it's possible to
write a resource block that installs the latest tar.gz package like
this:
@@ -90,7 +90,7 @@ See these guides for additional information about resources:
|