Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add license gating to kitchen-inspec #227

Closed
clintoncwolfe opened this issue Apr 8, 2019 · 4 comments
Closed

Add license gating to kitchen-inspec #227

clintoncwolfe opened this issue Apr 8, 2019 · 4 comments
Assignees
Labels

Comments

@clintoncwolfe
Copy link
Contributor

clintoncwolfe commented Apr 8, 2019

Describe the Enhancement:

Accept chef license when running InSpec via kitchen-inspec from Chef workstation. If running kitchen-inspec without a workstation install, apparently this is intended to run without license gating.

This is a major version change.

Describe the Need:

All InSpec 4+ users

@aaronlippold
Copy link

given that 4.0.8 does not allow for an escape hatch, should we prioritize this so we are not breaking kitchen ci/cd builds

@clintoncwolfe
Copy link
Contributor Author

4.0.8 is not a full release; we should talk about 4.3.2 and later.

Here is the plan:

  1. If you are calling Inspec::Runner yourself directly from your Ruby code, you are "using InSpec as a library" and are not subject to the license.
  2. If you use kitchen-inspec (which calls Inspec::Runner) from your custom gem install, my current understanding is that this is also a non-licensed use. I may be wrong here.
  3. If you use kicthen-inspec from a ChefDK or Chef Workstation installation, you will need to accept the license

So, we'll be adding code to kitchen-inspec to detect case 3 and prompt for license acceptance. Make sense?

@tas50
Copy link
Contributor

tas50 commented May 6, 2019

#2 is correct based on our past conversations with product

@tas50 tas50 closed this as completed Sep 17, 2019
@tas50
Copy link
Contributor

tas50 commented Sep 17, 2019

Closing this out based on the library usage of inspec here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants