itmustbejj · January 15, 2016 23:58
diff --git a/gistfile1.txt b/gistfile1.txt
 - If Delivery is a goal, policyfiles are in more of a wait-and-see mode
 - Policy groups replace environments, Policies replaces roles.
 - Policyfiles don't have a complete solution for environmental attributes. Best practice is to namespace attributes by env or use a discovery tool.
 - Without policy inheritence, consolidating all commmon cookbooks into a base cookbook that is included in mulitple policies, is the most sane way to manage dependency overlap in policies.
 - While gaining explicit versioning from policyfiles, any change to a common cookbook requires all/many policies to be regenerated. Some people want to have their cake and eat it too.
 - Policies work best on a per application level. Customers might be more successful if they follow an application cookbook pattern.
	- If Delivery is a goal, policyfiles are in more of a wait-and-see mode
	- Policy groups replace environments, Policies replaces roles.
	- Policyfiles don't have a complete solution for environmental attributes. Best practice is to namespace attributes by env or use a discovery tool.
	- Without policy inheritence, consolidating all commmon cookbooks into a base cookbook that is included in mulitple policies, is the most sane way to manage dependency overlap in policies.
	- While gaining explicit versioning from policyfiles, any change to a common cookbook requires all/many policies to be regenerated. Some people want to have their cake and eat it too.
	- Policies work best on a per application level. Customers might be more successful if they follow an application cookbook pattern.