Meta tags:
description= This document describes how to accept the End User License Agreement (EULA) and Master License and Services Agreement (MLSA).
For an overview of Chef’s license, see the Chef License documentation.;
Headings (most frequently used words):
chef, command, line, option, options, environment, variable, accept, the, products, config, file, habitat, infra, server, as, hab, packages, license, mlsa, eula, automate, client, inspec, workstation, remote, management, ci, errors, package, test, kitchen, knife, bootstrap, vagrant,
Text of the page (most frequently used words):
chef (292), the (157), license (101), #accept (77), infra (53), and (52), #server (51), overview (47), automate (37), habitat (36), file (35), install (35), with (33), command (32), builder (30), config (29), version (28), deployment (28), client (27), workstation (24), packages (24), aws (24), for (23), line (23), environment (23), about (22), configure (22), products (21), option (21), options (21), supermarket (21), variable (20), users (20), upgrade (20), hab (19), you (18), will (18), acceptance (18), manage (18), api (17), but (17), marker (17), ctl (17), node (17), product (16), management (16), inspec (16), can (16), prem (16), this (15), using (15), persist (15), reference (14), license_option (13), files (13), managed (13), create (13), test (12), mlsa (12), accepted (12), chef_license (12), accepting (12), future (12), again (12), nodes (12), backend (12), 360 (12), community (12), kitchen (11), package (11), user (11), instance (11), require (11), set (11), invocation (11), knife (10), eula (10), run (10), don (10), locally (10), configuration (10), compliance (10), platform (10), backup (10), restore (10), effortless (10), recovery (10), settings (10), saas (10), postgresql (10), started (10), opensearch (10), database (10), bootstrap (9), similar (9), example (9), reconfigure (9), system (9), use (8), remote (8), add (8), following (8), silent (8), attempts (8), services (8), data (8), cloud (8), resources (8), prerequisites (8), origin (8), disaster (8), requirements (8), desktop (8), guide (8), certificates (8), iam (8), prompt (7), accepts (7), are (6), all (6), when (6), persisted (6), stdout (6), these (6), yes (6), cookbooks (6), audit (6), migrate (6), log (6), style (6), security (6), cookstyle (6), cluster (6), supported (6), troubleshooting (6), update (6), logs (6), get (6), integrations (6), dashboard (6), applications (6), certificate (6), enterprise (6), other (5), see (5), page (5), policy (5), terms (5), licensing (5), vagrant (5), specify (5), local (5), that (5), sent (5), persisting (5), means (5), invocations (5), setting (5), service (5), process (5), commands (5), setup (5), directory (5), progress (4), trademarks (4), their (4), contents (4), have (4), covered (4), messaging (4), must (4), supervisor (4), also (4), your (4), cli (4), through (4), name (4), agreement (4), send (4), feedback (4), downloads (4), uninstall (4), organizations (4), groups (4), roles (4), saml (4), ldap (4), resource (4), packs (4), profiles (4), download (4), apis (4), upgrades (4), monitor (4), private (4), quick (4), start (4), deprecations (4), cops (4), firewalls (4), ports (4), authentication (4), authorization (4), high (4), availability (4), core (4), origins (4), profile (4), minio (4), single (4), cookbook (4), application (4), enrollment (4), infrastructure (4), getting (4), migration (4), courier (4), tokens (4), jobs (4), app (4), integration (4), external (4), elasticsearch (4), amazon (4), a2ha (4), premises (4), platforms (4), edition (4), names (3), one (3), its (3), errors (3), table (3), documentation (3), end (3), bootstrapping (3), fails (3), isn (3), installed (3), installation (3), has (3), support (3), from (3), export (3), distributed (3), key (3), interactive (3), during (3), runs (3), request (3), exit (3), licenses (3), filesystem (3), environments (3), matter (3), content (3), herein (2), software (2), corporation (2), subsidiaries (2), affiliates (2), appropriate (2), rights (2), any (2), reserved (2), respective (2), owners (2), does (2), 2026 (2), details (2), arguments (2), transfer (2), same (2), executable (2), without (2), yml (2), persistence (2), converge (2), provisioner (2), attempt (2), automatically (2), fail (2), behavior (2), tool (2), inspec_profile_name (2), exec (2), running (2), how (2), apply (2), etc (2), omnibus (2), allow (2), displayed (2), code (2), 172 (2), message (2), continue (2), successfully (2), than (2), root (2), empty (2), long (2), exists (2), won (2), typing (2), master (2), available (2), github (2), bags (2), clients (2), active (2), console (2), legacy (2), azure (2), remediation (2), release (2), notes (2), share (2), what (2), scaffolding (2), variables (2), pattern (2), attributehelper (2), attributedefault (2), useplatformhelpers (2), unnecessaryplatformcasestatement (2), unnecessaryoscheck (2), trueclassfalseclassresourceproperties (2), simplifyplatformmajorversioncheck (2), overlycomplexsupportsdependsmetadata (2), negatingonlyif (2), includerecipewithparentheses (2), immediatenotificationtiming (2), filemode (2), defaultcopyrightcomments (2), copyrightcommentformat (2), commentsentencespacing (2), commentformat (2), chefwhaaat (2), attributekeys (2), invalidlicensestring (2), insecurecookbookurl (2), includeresourceexamples (2), includeresourcedescriptions (2), includepropertydescriptions (2), emptymetadatafield (2), defaultmetadatamaintainer (2), sharing (2), sshprivatekey (2), unlessdefinedrequire (2), requirenethttps (2), legacypowershelloutmethods (2), gemspecrequirerubygems (2), gemspeclicense (2), ruby (2), usecreateifmissing (2), unnecessarynameproperty (2), unnecessarydesiredstate (2), suggestsmetadata (2), stringpropertywithnildefault (2), sensitivepropertyinresource (2), resourcewithnothingaction (2), replacesmetadata (2), recipemetadata (2), providesmetadata (2), propertywithrequiredanddefault (2), propertysplatregex (2), ohaiattributetostring (2), namepropertyisrequired (2), multipleplatformchecks (2), longdescriptionmetadata (2), groupingmetadata (2), doublecompiletime (2), customresourcewithallowedactions (2), conflictsmetadata (2), attributemetadata (2), aptrepositorynotifiesaptupdate (2), aptrepositorydistributiondefault (2), redundantcode (2), zipfileresource (2), windowszipfileusage (2), windowsscresource (2), windowsregistryuac (2), whyrunsupportedtrue (2), useszypperrepo (2), userequirerelative (2), usemultipackageinstalls (2), usecheflanguagesystemdhelper (2), usecheflanguageenvhelpers (2), usecheflanguagecloudhelpers (2), usebuildessentialresource (2), unnecessarymixlibshelloutrequire (2), unnecessarydependschef15 (2), unnecessarydependschef14 (2), sysctlparamresource (2), simplifyaptppasetup (2), shellouttochocolatey (2), shellouthelper (2), sevenziparchiveresource (2), setorreturninresources (2), respondtoresourcename (2), respondtoprovides (2), respondtoinmetadata (2), respondtocompiletime (2), resourcenamefrominitialize (2), resourceforcingcompiletime (2), providesfrominitialize (2), propertywithnameattribute (2), powershellscriptexpandarchive (2), powershellinstallwindowsfeature (2), powershellinstallpackage (2), powershellguardinterpreter (2), osxconfigprofileresource (2), opensslx509resource (2), opensslrsakeyresource (2), noderolesinclude (2), nodeinitpackage (2), minitesthandlerusage (2), macosxuserdefaults (2), libarchivefileresource (2), legacyberksfilesource (2), includingwindowsdefaultrecipe (2), includingohaidefaultrecipe (2), includingmixinshelloutinresources (2), includingaptdefaultrecipe (2), ifprovidesdefaultaction (2), foodcriticcomments (2), executetzutil (2), executesysctl (2), executesleep (2), executescexe (2), executeaptupdate (2), emptyresourceinitializemethod (2), dslincludeinresource (2), dependsonzyppercookbook (2), dependsonwindowsfirewallcookbook (2), dependsontimezonelwrpcookbook (2), dependsonopensslcookbook (2), dependsonlocalecookbook (2), dependsonkernelmodulecookbook (2), dependsonchocolateycookbooks (2), dependsonchefvaultcookbook (2), definitions (2), defineschefspecmatchers (2), defaultactionfrominitialize (2), declareactionclass (2), databaghelpers (2), customresourcewithattributes (2), cronmanageresource (2), crondfileortemplate (2), conditionalusingtest (2), classevalactionclass (2), chefgemnokogiri (2), allowedactionsfrominitialize (2), actionmethodinresource (2), modernize (2), searchforenvironmentsorroles (2), dependschefvault (2), cookbookusessearch (2), cookbookusesroles (2), cookbookusespolicygroups (2), cookbookusesenvironments (2), cookbookusesdatabags (2), chefvaultused (2), berksfile (2), windowsversionhelpers (2), windowstaskchangeaction (2), windowspackageinstallertypestring (2), windowsfeatureservermanagercmd (2), verifypropertyusesfileexpansion (2), useyamldump (2), usesruncommandhelper (2), usesdeprecatedmixins (2), useschefresthelpers (2), userdeprecatedsupportsproperty (2), useinlineresourcesdefined (2), useautomaticresourcename (2), searchusespositionalparameters (2), rubyblockcreateaction (2), ruby27keywordargumentwarnings (2), resourcewithoutunifiedtrue (2), resourceusesupdatedmethod (2), resourceusesproviderbasemethod (2), resourceusesonlyresourcename (2), resourceusesdslnamemethod (2), resourceoverridesprovidesmethod (2), resourceinheritsfromcompatresource (2), requirerecipe (2), powershellcookbookhelpers (2), policyfilecommunitysource (2), poisearchiveusage (2), partialsearchhelperusage (2), partialsearchclassusage (2), nodesetwithoutlevel (2), nodesetunless (2), nodeset (2), nodemethodsinsteadofattributes (2), nodedeepfetch (2), namepropertywithdefaultvalue (2), macosuserdefaultsglobalproperty (2), logresourcenotifications (2), localedeprecatedlcallproperty (2), librarianchefspec (2), legacyyumcookbookrecipes (2), legacynotifysyntax (2), launchddeprecatedhashproperty (2), includingyumdnfcompatrecipe (2), includingxmlrubyrecipe (2), hwrpwithoutunifiedtrue (2), hwrpwithoutprovides (2), foodcritictesting (2), foodcriticfile (2), executerelativecreateswithoutcwd (2), executepathproperty (2), erlcallresource (2), epicfail (2), eolauditmodeusage (2), easyinstallresource (2), deprecatedyumrepositoryproperties (2), deprecatedyumrepositoryactions (2), deprecatedwindowsversioncheck (2), deprecatedsudoactions (2), deprecatedshelloutmethods (2), deprecatedplatformmethods (2), deprecatedchefspecplatform (2), dependsonomnibusupdatercookbook (2), dependsonchefreportingcookbook (2), dependsonchefnginxcookbook (2), delivery (2), cookbooksdependsonself (2), cookbookdependsonpoise (2), cookbookdependsonpartialsearch (2), cookbookdependsoncompatresource (2), chocolateypackageuninstallaction (2), chefwindowsplatformhelper (2), chefsugarhelpers (2), chefspeclegacyrunner (2), chefspeccoveragereport (2), chefshellout (2), chefrewind (2), chefhandlerusessupports (2), chefhandlerrecipe (2), cheffile (2), chefdkgenerators (2), tmppath (2), supportsmustbefloat (2), serviceresource (2), scopedfileexist (2), resourcewithnoneaction (2), resourcesetsnameproperty (2), resourcesetsinternalproperties (2), propertywithouttype (2), powershellscriptdeletefile (2), powershellfileexists (2), opensslpasswordhelpers (2), octalmodeasstring (2), notifiesactionnotsymbol (2), nodenormalunless (2), nodenormal (2), metadatamissingversion (2), metadatamissingname (2), metadatamalformeddepends (2), malformedplatformvalueforplatformhelper (2), macosuserdefaultsinvalidtype (2), lazyinresourceguard (2), lazyevalnodeattributedefaults (2), invalidversionmetadata (2), invalidplatformvalueforplatformhelper (2), invalidplatformvalueforplatformfamilyhelper (2), invalidplatformmetadata (2), invalidplatformincase (2), invalidplatformhelper (2), invalidplatformfamilyincase (2), invalidplatformfamilyhelper (2), invalidnotificationtiming (2), invalidnotificationresource (2), invaliddefaultaction (2), invalidcookbookname (2), incorrectlibraryinjection (2), emptyresourceguard (2), dnfpackageallowdowngrades (2), cookbookusesnodesave (2), conditionalrubyshellout (2), chefapplicationfatal (2), blockguardwithonlystring (2), correctness (2), list (2), v25 (2), v26 (2), tuning (2), failure (2), optional (2), usage (2), tiered (2), airgap (2), capacity (2), planning (2), plan (2), base (2), 2025 (2), refresh (2), strategy (2), account (2), membership (2), rbac (2), keys (2), rotate (2), ssl (2), certs (2), separate (2), scale (2), frontend (2), artifactory (2), artifact (2), store (2), warm (2), spare (2), env (2), connect (2), windows_update_settings (2), windows_power_management (2), windows_password_policy (2), windows_ie_esc (2), windows_firewall (2), windows_disk_encryption (2), windows_desktop_winrm_settings (2), windows_desktop_screensaver (2), windows_defender_exclusion (2), windows_defender (2), windows_choco_installer (2), windows_automatic_logout (2), windows_app_management (2), windows_admin_control (2), rescue_account (2), macos_power_management (2), macos_password_policy (2), macos_firewall (2), macos_disk_encryption (2), macos_desktop_screensaver (2), macos_automatic_software_updates (2), macos_automatic_logout (2), macos_app_management (2), macos_admin_control (2), windows (2), macos (2), zero (2), touch (2), redirect (2), sso (2), opsworks (2), skills (2), administration (2), guides (2), enroll (2), clis (2), non (2), san (2), best (2), practices (2), feature (2), flags (2), architecture (2), administrator (2), incident (2), servicenow (2), marketplace (2), scan (2), reports (2), eas (2), event (2), feed (2), teams (2), policies (2), actions (2), projects (2), credentials (2), lifecycle (2), feeds (2), notifications (2), cleanup (2), monitoring (2), centralize (2), large (2), report (2), ingestion (2), invalid (2), login (2), telemetry (2), session (2), timeout (2), disclosure (2), panel (2), banner (2), collection (2), topics (2), manager (2), bastion (2), new (2), machine (2), sudo (2), password (2), rds (2), vpc (2), cidr (2), load (2), balancer (2), faqs (2), performance (2), benchmarks (2), rotation (2), self (2), signed (2), custom (2), view (2), verify (2), generation (2), remove (2), place (2), existing (2), efs (2), back (2), object (2), storage (2), customer (2), airgapped (2), tutorial (2), shortcodes (2), front (2), reuse (2), hugo (2), procedures (2), tables (2), headings (2), notices (2), markdown (2), lists (2), linking (2), formatting (2), tools (2), house (2), contribute (2), docs (2), guidelines (2), contributions (2), commercial (2), script (2), versions (2), training (2), blog (2), main (2), certain, used, registered, countries, markings, contained, inclusion, not, imply, endorsement, affiliation, sponsorship, between, copyright, last, modified, april, cookie, privacy, trademark, site, map, provision, chef_zero, usually, already, been, across, transparently, installs, first, they, perform, flow, before, allowing, uses, library, gem, packaged, part, way, under, verifier, section, disable, every, detects, transferred, owned, installing, converges, succeed, copying, aim, workflow, affected, differences, documented, below, terraform, provider, deprecated, packer, bundled, several, invoking, embedded, well, applies, each, own, against, more, information, group, updates, echo, default, 100, mode, correct, values, value, typically, some, kind, because, supervisors, interactivity, instead, those, then, sends, situations, where, multiple, both, home, automated, replace, hab_license, silently, either, methods, argument, walks, after, browser, follow, prompts, var, opt, types, skips, printing, printed, type, anything, rejects, adds, accepted_licenses, ways, two, document, describes, menu, search, skip,
Text of the page (random words):
owspackageinstallertypestring windowstaskchangeaction windowsversionhelpers chef effortless berksfile chefvaultused cookbookusesdatabags cookbookusesenvironments cookbookusespolicygroups cookbookusesroles cookbookusessearch dependschefvault searchforenvironmentsorroles chef modernize actionmethodinresource allowedactionsfrominitialize chefgemnokogiri classevalactionclass conditionalusingtest crondfileortemplate cronmanageresource customresourcewithattributes databaghelpers declareactionclass defaultactionfrominitialize defineschefspecmatchers definitions dependsonchefvaultcookbook dependsonchocolateycookbooks dependsonkernelmodulecookbook dependsonlocalecookbook dependsonopensslcookbook dependsontimezonelwrpcookbook dependsonwindowsfirewallcookbook dependsonzyppercookbook dslincludeinresource emptyresourceinitializemethod executeaptupdate executescexe executesleep executesysctl executetzutil foodcriticcomments ifprovidesdefaultaction includingaptdefaultrecipe includingmixinshelloutinresources includingohaidefaultrecipe includingwindowsdefaultrecipe legacyberksfilesource libarchivefileresource macosxuserdefaults minitesthandlerusage nodeinitpackage noderolesinclude opensslrsakeyresource opensslx509resource osxconfigprofileresource powershellguardinterpreter powershellinstallpackage powershellinstallwindowsfeature powershellscriptexpandarchive propertywithnameattribute providesfrominitialize resourceforcingcompiletime resourcenamefrominitialize respondtocompiletime respondtoinmetadata respondtoprovides respondtoresourcename setorreturninresources sevenziparchiveresource shellouthelper shellouttochocolatey simplifyaptppasetup sysctlparamresource unnecessarydependschef14 unnecessarydependschef15 unnecessarymixlibshelloutrequire usebuildessentialresource usecheflanguagecloudhelpers usecheflanguageenvhelpers usecheflanguagesystemdhelper usemultipackageinstalls userequirerelative useszypperrepo whyrunsupportedtrue windowsregistryuac windowsscresource windowszipfileusage zipfileresource chef redundantcode aptrepositorydistributiondefault aptrepositorynotifiesaptupdate attributemetadata conflictsmetadata customresourcewithallowedactions doublecompiletime groupingmetadata longdescriptionmetadata multipleplatformchecks namepropertyisrequired ohaiattributetostring propertysplatregex propertywithrequiredanddefault providesmetadata recipemetadata replacesmetadata resourcewithnothingaction sensitivepropertyinresource stringpropertywithnildefault suggestsmetadata unnecessarydesiredstate unnecessarynameproperty usecreateifmissing chef ruby gemspeclicense gemspecrequirerubygems legacypowershelloutmethods requirenethttps unlessdefinedrequire chef security sshprivatekey chef sharing defaultmetadatamaintainer emptymetadatafield includepropertydescriptions includeresourcedescriptions includeresourceexamples insecurecookbookurl invalidlicensestring chef style attributekeys chefwhaaat commentformat commentsentencespacing copyrightcommentformat defaultcopyrightcomments filemode immediatenotificationtiming includerecipewithparentheses negatingonlyif overlycomplexsupportsdependsmetadata simplifyplatformmajorversioncheck trueclassfalseclassresourceproperties unnecessaryoscheck unnecessaryplatformcasestatement useplatformhelpers inspec deprecations attributedefault attributehelper effortless pattern effortless overview quick start effortless audit effortless config variables and config what is scaffolding supermarket about supermarket share cookbooks private supermarket about private supermarket install configure backup and restore monitor log files upgrades reference supermarket ctl supermarket api release notes chef 360 platform chef automate chef backend chef download apis chef habitat chef infra client chef infra server chef inspec chef local license service chef manage chef migrate chef supermarket chef workstation chef compliance chef compliance audit profiles chef compliance remediation chef cloud resource packs aws cloud resources azure cloud resources legacy chef manage about the management console uninstall manage rb chef manage ctl active directory ldap configure saml clients cookbooks data bags environments nodes roles organizations groups users uninstall available on github downloads send feedback support accept the chef license table of contents this document describes how to accept the end user license agreement eula and master license and services agreement mlsa for an overview of chef s license see the chef license documentation chef has two licenses master license and services agreement mlsa and end user license agreement eula accept the chef mlsa you can accept the chef mlsa using one of the following ways when running chef product name ctl reconfigure the chef mlsa is printed type yes to accept it anything other than typing yes rejects the chef mlsa and the upgrade process will exit typing yes adds a license accepted file to the etc chef accepted_licenses product name file as long as this file exists in this directory the chef mlsa is accepted and the reconfigure process won t prompt for yes run the chef product name ctl reconfigure command using the chef license accept option this automatically types yes and skips printing the chef mlsa add a license accepted file to the var opt product name directory the contents of this file don t matter as long as this file exists in this directory the chef mlsa is accepted and the reconfigure process won t prompt for yes chef automate the chef automate reconfigure tool automate ctl walks users through the install and setup of chef automate accept the chef mlsa after that in the browser follow the in product prompts accept the chef eula if no command line argument or environment variable is set chef products attempt to request acceptance through an interactive prompt if the prompt can t be displayed the product will fail with an exit code 172 if the product attempts to persist the accepted license and fails a message is sent to stdout but product invocation will continue successfully in a future invocation you must accept the chef license again see license file persistence for details about persisted marker files chef habitat you can accept the chef license using a hab cli command or with an environment variable if the license isn t accepted through either of these methods chef habitat will request that you accept the license through an interactive prompt options chef habitat accepts the following license acceptance options accept 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 accept no persist accept the license silently but no marker file is persisted future invocation will require accepting the license again command line option you can use the hab cli to accept the chef license hab license license_option environment variable you can set an environment variable to accept the chef license for example export hab_license license_option hab v replace license_option with one of the chef license options ci environment to accept the chef license in ci or other automated environments if your hab commands run as root create an empty file on the filesystem at hab accepted licenses habitat if your hab commands run as a user other than root create an empty file at home hab accepted licenses habitat for situations where hab commands run as multiple users create both files errors if the chef habitat license prompt can t be displayed then the product fails with an exit code 172 if chef habitat can t persist the accepted license it sends a message stdout but the product invocation will continue successfully you must accept the chef license again in a future invocation chef products as hab packages chef products are also distributed as hab packages when you install chef products using chef habitat those products also request license acceptance chef server products as hab packages the following chef server products are distributed as hab packages that chef habitat runs as a supervisor chef infra server chef automate chef supermarket server products are typically installed and managed by some kind of process supervisor chef server products don t allow interactive license acceptance because process supervisors don t allow interactivity instead accept the chef license during the reconfigure command or upgrade command for the omnibus ctl command command line option accept the chef license with the command line option for example chef server ctl reconfigure chef license license_option environment variable accept the chef license with an environment variable for example chef_license license_option supermarket ctl reconfigure config file you can also accept the chef license using the omnibus configuration file specify chef_license accept in the chef server rb or supermarket rb configuration chef infra client chef infra client accepts a license using a command line option environment variable or config file options chef infra client accepts the following license acceptance options accept 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 accept silent similar to accept but no messaging is sent to stdout accept no persist similar to accept silent but no marker file is persisted future invocation will require accepting the license again command line option accept the chef license with a command line invocation chef client chef license license_option environment variable accept the chef license by setting an environment variable for example export chef_license license_option chef client option value config file you can accept the chef license with the chef infra client or knife config files on a workstation you can set this in the chef config rb or chef knife rb files and on a node you can set this in the etc chef client rb file chef_license license_option chef infra server when installed as a system package users accept the chef license with the chef server ctl command or with the chef server rb file options chef infra server accepts the following license acceptance options accept 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 accept silent similar to accept but no messaging is sent to stdout accept no persist similar to accept silent but no marker file is persisted future invocation will require accepting the license again command line option you can accept the chef license with the chef server ctl command chef server ctl reconfigure chef license license_option config file you can accept the chef license with the chef server rb file chef_license license_option chef habitat package chef infra server is also distributed as a hab package and run using the chef habitat supervisor in this mode users accept the chef license by setting the correct configuration values the key is chef_license acceptance for example against a supervisor running chef infra server run echo chef_license acceptance accept hab config apply server default 100 see the chef habitat config updates documentation for more information about how to apply this configuration to a service group chef inspec chef inspec accepts a license using a command line option or environment variable options chef inspec accepts the following license acceptance options accept 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 accept silent similar to accept but no messaging is sent to stdout accept no persist similar to accept silent but no marker file is persisted future invocation will require accepting the license again command line option accept the chef license with a command line invocation inspec exec inspec_profile_name chef license license_option environment variable accept the chef license by setting an environment variable for example export chef_license license_option inspec exec inspec_profile_name chef workstation chef workstation is bundled with several chef products when invoking the chef command line tool and accepting the chef license you must accept the license for all the embedded products as well the same license applies to all products but each product must have its own license acceptance options chef workstation accepts the following license acceptance options accept 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 accept silent similar to accept but no messaging is sent to stdout accept no persist similar to accept silent but no marker file is persisted future invocation will require accepting the license again command line option use the chef executable to accept the chef license for chef workstation chef infra client and chef inspec chef command chef license license_option remote management products if a user has accepted the appropriate product license locally the following remote management products that can install or manage chef products on a remote instance will transfer the chef license acceptance to the remote instance test kitchen knife bootstrap in chef infra client chef run in chef workstation packer terraform chef provider deprecated vagrant for example if a user has accepted the chef infra client license locally and converges a test kitchen instance with the chef provisioner it will succeed by copying the acceptance to the remote instance we aim to support this behavior so workstation users don t have their workflow affected but any differences from that behavior are documented below test kitchen test kitchen isn t owned by or covered by the chef license but installing chef infra client on a test instance is covered by the eula without accepting the chef license the converge will fail on the test instance users can set the chef_license environment variable or add chef_license accept to their provisioner config in the kitchen yml file if you specify accept test kitchen will attempt to persist the license acceptance locally if test kitchen detects a local license marker file acceptance is automatically transferred to the test instance to disable this persistence specify accept no persist on every test instance converge kitchen inspec uses chef inspec as a library and isn t covered by the eula when installed as a gem but is covered by the eula when packaged as part of the chef workstation installation accept the license in a similar way to the chef infra client license specify the chef_license environment variable specify the chef_license config under the verifier section in kitchen yml or persist the acceptance locally knife bootstrap you don t have to accept the eula to use the knife executable but a chef infra client instance does require eula acceptance using knife boots...
|
