Skip to content

Conversation

@Stromweld
Copy link
Contributor

Description

RFC proposal

Signed-off-by: Corey Hemminger <[email protected]>
@Stromweld
Copy link
Contributor Author

This requires #1 to be merged first but setting up for review

@damacus
Copy link

damacus commented Nov 4, 2025

I had expected to find something to comment about but this looks good to me!

@damacus damacus requested review from damacus, tas50 and xorima November 4, 2025 20:50
damacus
damacus previously approved these changes Nov 4, 2025
@damacus damacus changed the title rfc 0001 decouple chef provisioner [RFC-001] decouple chef provisioner Nov 4, 2025
@damacus damacus changed the title [RFC-001] decouple chef provisioner [RFC-001] Decouple Chef provisioner Nov 4, 2025
@Stromweld
Copy link
Contributor Author

for the initial provisioner extraction maintaining current function naming wise what makes sense and would mean the most to others kitchen-legacy-chef or kitchen-omnitruck-chef? I'm leaning toward the latter as name then associates it with omnitruck and helps tie in when omnitruck gets shutdown that that gem will effectively be dead.

@damacus
Copy link

damacus commented Nov 5, 2025

Omni truck makes it sound less ominous and is clearer. Hopefully that pushes the information out to users that it's being deprecated

@Stromweld
Copy link
Contributor Author

Plan is to also add info logs warning of the deprecation and suggesting switch to chef enterprise or cinc provisioners.

…ed kitchen-legacy-chef to kitchen-omnibus-chef

Signed-off-by: Corey Hemminger <[email protected]>
@damacus damacus merged commit 933789d into main Nov 12, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants