Conversation
Updates the InSpec 7 licensing documentation to reflect the updated licensing model, including download-based enforcement and clarification around official and non-official distribution channels.
✅ Deploy Preview for chef-inspec-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
clintoncwolfe
left a comment
clintoncwolfe
left a comment
There was a problem hiding this comment.
Some wording issues.
content/install/license.md
Outdated
|
|
||
| Chef InSpec 7 introduces an updated licensing model designed to simplify usage while maintaining compliance across distribution channels. | ||
|
|
||
| For software downloaded from official Progress distribution channels, license enforcement does not occur at runtime. Instead, license verification may occur during the download process. |
There was a problem hiding this comment.
Avoid the term "license enforcement" - license is always enforced in the sense of requirring a EULA. License key is not required sometimes.
There was a problem hiding this comment.
I’ve updated the wording to remove the “license enforcement” terminology and removed the Infra Client workflow examples since they aren’t relevant to InSpec. The updates are included in the second commit.
content/install/license.md
Outdated
| Some workflows may download Chef binaries as part of their execution. Examples include: | ||
|
|
||
| - `knife bootstrap` | ||
| - `kitchen converge` |
There was a problem hiding this comment.
This isn't relevant to InSpec. This is only used with Chef Infra CLient. THe only thing people are wondering abut is is kitchen verify will require a license and it will not.
Updated licensing explanation to avoid "license enforcement" terminology and removed Infra Client workflow examples that are not relevant to InSpec.
2 participants
Updates the InSpec 7 licensing documentation to reflect the updated licensing model introduced for Progress Chef products.
Description
This change updates the licensing explanation in the InSpec documentation to reflect the current licensing behavior. The previous text described licensing based only on distribution type (Habitat package vs Ruby gem).
The updated section clarifies that:
knife bootstrapandkitchen converge) may require a license if the binaries are retrieved from Chef APIs.Chef InSpec versions
InSpec 7
Issues resolved
N/A
Related PRs
N/A
Checklist