You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add text about EULA
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
* Fix heading levels
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
---------
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Copy file name to clipboardExpand all lines: content/license/_index.md
+49Lines changed: 49 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,9 @@ weight = 11
11
11
12
12
This document outlines the licensing requirements and enforcement policies for Chef Infra Client 19.
13
13
14
+
Depending on the distribution you download and install, you may have to add a license key to run Chef Infra Client.
15
+
You must also [accept the Chef End User License Agreement (Chef EULA)](#accept-the-end-user-license-agreement) when you first run Chef Infra Client 19.
16
+
14
17
## Licensing requirements
15
18
16
19
Chef Infra Client 19 has different licensing requirements depending on the distribution you download.
@@ -97,3 +100,49 @@ To set a license key with the CLI interactive dialog, follow these steps:
97
100
```
98
101
99
102
After entering the license key, Chef Infra Client verifies your license and the run completes.
103
+
104
+
## Accept the End User License Agreement
105
+
106
+
When you first run Chef Infra Client 19, you must accept the End User License Agreement (EULA).
107
+
108
+
Chef Infra Client accepts a license using a command line option, environment variable, or config file.
109
+
110
+
### Options
111
+
112
+
Chef Infra Client accepts the following license acceptance options:
113
+
114
+
`accept`
115
+
: Accept the license and attempts to persist a marker file locally. Persisting these marker files means future invocations don't require accepting the license again.
116
+
117
+
`accept-silent`
118
+
: Similar to `accept`, but no messaging is sent to STDOUT.
119
+
120
+
`accept-no-persist`
121
+
: Similar to `accept-silent`, but no marker file is persisted. Future invocation will require accepting the license again.
122
+
123
+
### Command line option
124
+
125
+
Accept the Chef License with a command line invocation.
126
+
127
+
```sh
128
+
chef-client --chef-license <LICENSE_OPTION>
129
+
```
130
+
131
+
### Environment variable
132
+
133
+
Accept the Chef License by setting an environment variable. For example:
134
+
135
+
```sh
136
+
export CHEF_LICENSE="<LICENSE_OPTION>"
137
+
chef-client OPTION VALUE
138
+
```
139
+
140
+
### Config file
141
+
142
+
You can accept the Chef License with the Chef Infra Client or Knife config files.
143
+
144
+
On a workstation, you can set this in the [`~/.chef/config.rb` or `~/.chef/knife.rb` files](/workstation/config_rb/), and on a node you can set this in the [`/etc/chef/client.rb`]({{< relref "/config_rb_client">}}) file.
0 commit comments