Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Remove policyfile_zero kitchen provisioner #1423

Open
danielsdeleo opened this issue Oct 4, 2017 · 0 comments
Open

Remove policyfile_zero kitchen provisioner #1423

danielsdeleo opened this issue Oct 4, 2017 · 0 comments
Labels
Components: Policyfile Issues realted to Policyfiles

Comments

@danielsdeleo
Copy link
Contributor

danielsdeleo commented Oct 4, 2017 •
edited
Loading

Description

Kitchen now natively supports policyfiles, so there is no reason to use the policyfile_zero provisioner. We might want to remove it like this:

  • ChefDK 2.x: add deprecation warnings
  • ChefDK 3.0: Remove all functionality, but leave the file in place. If someone tries to use it, kitchen should print migration instructions and exit with an error.
  • ChefDK 4.0: remove everything
@danielsdeleo danielsdeleo added this to the Accepted Major milestone Oct 4, 2017
@tas50 tas50 changed the title ChefDK3 - Remove policyfile_zero kitchen provisioner Remove policyfile_zero kitchen provisioner Aug 7, 2018
@cheeseplus cheeseplus added the Components: Policyfile Issues realted to Policyfiles label Aug 25, 2018
@jonsmorrow jonsmorrow removed this from the Accepted Major milestone Feb 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Components: Policyfile Issues realted to Policyfiles
Milestone
No milestone
Development

No branches or pull requests
3 participants
@danielsdeleo @cheeseplus @jonsmorrow