Skip to content

Commit 31a24af

Browse files
authored
Merge pull request #105254 from TomArcherMsft/chef-task-379
Chef - Task 379
2 parents bcc64a2 + cc04298 commit 31a24af

24 files changed

+344
-378
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48865,6 +48865,11 @@
4886548865
"source_path": "articles/media-services/previous/media-services-develop-video-players.md",
4886648866
"redirect_url": "/azure/media-services",
4886748867
"redirect_document_id": false
48868+
},
48869+
{
48870+
"source_path": "articles/virtual-machines/windows/chef-automation.md",
48871+
"redirect_url": "/azure/chef/chef-automation",
48872+
"redirect_document_id": true
4886848873
}
4886948874
]
4887048875
}

articles/virtual-machines/windows/chef-automation.md renamed to articles/chef/chef-automation.md

Lines changed: 317 additions & 356 deletions
Large diffs are not rendered by default.

articles/chef/chef-extension-portal.md

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Install the Chef client from the Azure portal
33
description: Learn how to deploy and configure your Chef client from the Azure portal
44
keywords: azure, chef, devops, client, install, portal
5-
ms.date: 05/15/2018
5+
ms.date: 02/22/2020
66
ms.topic: article
77
---
88

@@ -74,29 +74,30 @@ In this section, you'll first use the Azure portal to create a Linux machine. Du
7474
1. On the **Install extension** tab, specify the following values, and then select **OK**.
7575

7676
- **Chef Server URL** - Enter the Chef Server URL that includes the organization name, for example, *https://api.chef.io/organization/mycompany*.
77-
- **Chef Node Name** - Enter the Chef Node name. This can be any value.
78-
- **Run List** - Enter the Chef run list that is added to the machine. This can be left blank.
79-
- **Validation Client Name** - Enter the Chef Validation Client Name. for example, *tarcher-validator*.
77+
- **Chef Node name** - Enter the Chef Node name.
78+
- **Run list** - Enter the Chef run list that is added to the machine. This value can be left blank.
79+
- **Validation client name** - Enter the Chef Validation Client Name. for example, `tarcher-validator`.
8080
- **Validation Key** - Select a file containing the validation key used when bootstrapping your machines.
81-
- **Client Configuration File** - Select a configuration file for chef-client. This can be left blank.
82-
- **Chef Client version** - Enter the version of the chef client to install. This can be left blank. A blank value installs the latest version.
81+
- **Client configuration file** - Select a configuration file for chef-client. This value can be left blank.
82+
- **Chef Client version** - Enter the version of the chef client to install. This value can be left blank, which installs the latest version.
8383
- **SSL Verification Mode** - Select either **None** or **Peer**. *None* was selected for the demo.
84-
- **Chef Environment** - Enter the Chef environment this node should be a member of. This can be left blank.
85-
- **Encrypted Databag Secret** - Select a file containing the secret for the Encrypted Databag this machine should have access to. This can be left blank.
86-
- **Chef Server SSL Certificate** - Select the SSL Certificate assigned to your Chef Server. This can be left blank.
84+
- **Chef Environment** - Enter the Chef environment this node should be a member of. This value can be left blank.
85+
- **Encrypted data bag secret** - Select a file containing the secret for the encrypted data bag this machine needs to access. This value can be left blank.
86+
- **Chef Server SSL certificate** - Select the SSL certificate assigned to your Chef Server. This value can be left blank.
8787

8888
![Installing the Chef Server on a Linux virtual machine](./media/chef-extension-portal/install-extension.png)
8989

90-
1. When returning to the **Extensions** tab, select **OK**.
90+
1. When the **Extensions** tab displays, select **OK**.
9191

92-
1. When returning to the **Settings** tab, select **OK**.
92+
1. When the **Settings** tab displays, select **OK**.
9393

94-
1. When returning to the **Create** tab (this represents a summary of the options you selected and entered), verify the information as well as the **Terms of use**, and select **Create**.
94+
1. When the **Create** tab displays, you see a summary of the options you selected and entered. Verify the information as well as the **Terms of use**, and select **Create**.
9595

9696
When the process of creating and deploying the virtual machine with the Chef Extension is complete, a notification indicates the success or failure of the operation. In addition, the resource page for the new virtual machine automatically opens in the Azure portal once it's been created.
9797

9898
![Installing the Chef Server on a Linux virtual machine](./media/chef-extension-portal/resource-created.png)
9999

100100
## Next steps
101101

102-
- [Create a Windows virtual machine on Azure using Chef](/azure/virtual-machines/windows/chef-automation)
102+
> [!div class="nextstepaction"]
103+
> [Create a Windows virtual machine on Azure using Chef](chef-automation.md)

articles/chef/chef-overview.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Using Chef with Azure
33
description: Introduction to using Chef to configure and test your Azure infrastructure
44
keywords: azure, chef, devops, virtual machines, overview, automate
5-
ms.date: 05/15/2018
5+
ms.date: 02/22/2020
66
ms.topic: article
77
---
88

@@ -12,7 +12,7 @@ ms.topic: article
1212
This article describes the benefits of using Chef to manage Azure infrastructure.
1313

1414
## Chef Extension on Azure
15-
Provision a virtual machine with Chef Client running as a background service with the [Chef Extension](https://docs.microsoft.com/azure/chef/chef-extension-portal) on the Azure Portal. Once provisioned, these virtual machines are ready to be managed by a Chef server.
15+
Provision a virtual machine with Chef Client running as a background service with the [Chef Extension](https://docs.microsoft.com/azure/chef/chef-extension-portal) on the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040). Once provisioned, these virtual machines are ready to be managed by a Chef server.
1616

1717
## Chef Cloud Shell
1818
Use Chef Workstation directly in Azure Cloud Shell! Run all of your Chef utilities and InSpec right from Cloud Shell. You can utilize the Chef commands from:
@@ -22,7 +22,6 @@ Use Chef Workstation directly in Azure Cloud Shell! Run all of your Chef utiliti
2222
* [inspec](https://www.inspec.io/docs/reference/cli/)
2323
* [knife](https://docs.chef.io/knife.html)
2424
* [cookstyle](https://docs.chef.io/cookstyle.html)
25-
* [foodcritic](https://docs.chef.io/foodcritic.html)
2625
* [chef-run](https://www.chef.sh/docs/chef-workstation/getting-started/)
2726

2827
Combine our command utilities with the other tools available in Cloud Shell, such as `git`, `az-cli`, and `terraform`, and write your infrastructure and compliance automation from the browser.
@@ -35,4 +34,4 @@ Supported by Chef, the [Chef Automate Azure Marketplace solution](https://azurem
3534

3635
## Next steps
3736

38-
* [Create a Windows virtual machine on Azure using Chef](/azure/virtual-machines/windows/chef-automation)
37+
* [Create a Windows virtual machine on Azure using Chef](chef-automation.md)

articles/chef/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,4 +50,4 @@ landingContent:
5050
- linkListType: tutorial
5151
links:
5252
- text: Create a Windows VM
53-
url: /azure/virtual-machines/windows/chef-automation?/azure/chef/toc.json&bc=/azure/bread/toc.json
53+
url: chef-automation.md

0 commit comments

Comments
 (0)