-
Notifications
You must be signed in to change notification settings - Fork 132
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
Removal of cmtool.sh #36
Comments
Sure. We've come up with a simpler way for users to inject custom functionality in these templates as boxes are built - the Boxcutter never published boxes with CM tools baked in, we never ran builds with Further, most CM tools these days are designed with a system to dynamically inject/bootstrap the CM tool into an environment, so you always have the latest version, which is a much better approach than trying to bake a version of the tool into an image. The philosophy behind the images has always been that they are JEOS images "Just Enough OS" for a configuration management tool. It's just that in the past "just enough" usually also meant the CM tool itself as many CM systems didn't have great ways to bootstrap themselves. Now it seems like CM installers have evolved and matured that's not needed so much. That being said, you can still do what you used to do via |
Thanks for the explanation. I'm probably one of the few people who uses the saltstack part of Thanks for your work on this project! |
Hello @annawake, could you explain the rationale behind removing
cmtool.sh
in f39c56c? Thanks.The text was updated successfully, but these errors were encountered: