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

Move knife-acl gem commands into chef in their own namespaces #9292

Merged
merged 1 commit into from Jan 30, 2020

Conversation

tas50
Copy link
Contributor

@tas50 tas50 commented Jan 28, 2020

Ship these knife commands so we can kill off knife-acl, but move them under their own namespaces.

Signed-off-by: Tim Smith tsmith@chef.io

@tas50 tas50 requested review from a team as code owners January 28, 2020 18:59
@lamont-granquist
Copy link
Contributor

These all work against normal chef-server though (after the single-org open source chef-11 server was killed off)

@tas50 tas50 force-pushed the knife_acl branch 2 times, most recently from fb689c6 to 6e9afc8 Compare January 28, 2020 22:15
@tas50 tas50 changed the title WIP: Move knife-acl gem commands into knife hosted namespace WIP: Move knife-acl gem commands into chef in their own namespaces Jan 28, 2020
@tas50
Copy link
Contributor Author

tas50 commented Jan 28, 2020

Reworked to just stick them into the appropriate namespaces

Ship these knife commands so we can kill off knife-acl, but move them under their own namespaces.

Signed-off-by: Tim Smith <tsmith@chef.io>
@tas50 tas50 changed the title WIP: Move knife-acl gem commands into chef in their own namespaces Move knife-acl gem commands into chef in their own namespaces Jan 30, 2020
@tas50 tas50 merged commit 0f2db94 into master Jan 30, 2020
@chef-expeditor chef-expeditor bot deleted the knife_acl branch January 30, 2020 18:35
@lock
Copy link

lock bot commented Feb 13, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 13, 2020
@tas50 tas50 added the Type: Breaking Change Changes the way existing features work in a way that affects users. label Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Breaking Change Changes the way existing features work in a way that affects users.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants