Switch to Policyfile #78
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#78
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
knife-solo is deprecated (https://github.com/matschaffer/knife-solo), and I have just had an issue with an old attribute being persisted into the node file for barnard in my home directory on barnard (
~/chef-solo/nodes/barnard.kosmos.org.json
) that was hard to figure outWe might be able to use chef-run together with Policyfile to replicate our current knife-solo setup
In my experience
chef-run
is far from ready: error messages are cryptic, I can't find a way to set a policy group (replaces environments) or to load data bag items, which is a deal breakerPolicyfile seem to be well supported when using Chef Server by now, but without one it is hard to work with. I would put this issue on hold until a tool that supports Policyfiles without a Chef Server is released, because running Chef Server for only two servers is overkill.
OK. Created an icebox milestone for things on hold.
Switch to Policyfile, replace knife-soloto Switch to PolicyfileI have removed this one from the Icebox and changed its title, Knife-Zero supports Policyfile: https://knife-zero.github.io/tips/with_policyfile/
@greg Is this issue still relevant in your opinion?
I think we can close this one, I haven't looked at Policyfiles since then. We can always reopen it if we feel the need to investigate again