You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On chef-client re-runs I noticed sometimes chef-acl would report (up to date) but then other times it reported its updating even though no acls need to be changed. Seems like the order it finds out about current acls actually matters as the from and to lists below have same values but from list is unsorted whereas to list is sorted alphabetically.
* chef_acl[containers/sandboxes] action create
- update acl containers/sandboxes at containers/sandboxes
- create, update, delete: update groups from ["dev", "admins"] to ["admins", "dev"]
- read: update groups from ["clients", "users", "dev", "admins", "ops", "noc"] to ["admins", "clients", "dev", "noc", "ops", "users"]
The text was updated successfully, but these errors were encountered:
On chef-client re-runs I noticed sometimes chef-acl would report
(up to date)
but then other times it reported its updating even though no acls need to be changed. Seems like the order it finds out about current acls actually matters as thefrom
andto
lists below have same values butfrom
list is unsorted whereasto
list is sorted alphabetically.The text was updated successfully, but these errors were encountered: