summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Smith <tsmith84@gmail.com>2021-01-06 17:03:28 -0800
committerTim Smith <tsmith84@gmail.com>2021-01-06 17:03:28 -0800
commit35517e177668fd01e2b71fb01c4145c3bd5f5122 (patch)
tree263d79f683b42dfdc45e127f4dfbab17e2404052
parent6f83e111773c0408435dc3eccb2d065505d8a381 (diff)
downloadchef-35517e177668fd01e2b71fb01c4145c3bd5f5122.tar.gz
Better describe the knife.rb -> config.rb migration
Signed-off-by: Tim Smith <tsmith@chef.io>
-rw-r--r--RELEASE_NOTES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 9ce011513e..ea4b5a8861 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -4492,7 +4492,7 @@ We've spent a considerable amount of time testing and fixing the `windows_task`
## Credentials handling
-Previously, chef on the workstation used `knife.rb` or `config.rb` to handle credentials. This didn't do a great job when interacting with multiple Chef servers, leading to the need for tools like `knife_block`. We've added support for a credentials file that can contain configuration for many Chef servers (or organizations), and we've made it easy to indicate which account you mean to use.
+Previously, the `knife` CLI used `knife.rb` or `config.rb` to handle credentials. This didn't do a great job when interacting with multiple Chef servers, leading to the need for tools like `knife_block`. We've added support for a credentials file that can contain configuration for many Chef servers (or organizations), and we've made it easy to indicate which account you mean to use.
## New deprecations