Home > developer > content development > Pack policy
Policies can also be specified as part of the pack definition. This enables policy evaluation on all CIs (components, attachments, platform variables, monitors) under the platform for a given pack. The violated policies can then be fixed to avoid issues further down the application lifecycle.
The policy definitions are added to the pack “.rb” file in a given circuit. Following are few examples of pack based policies.
policy "env-profile",
:description => 'custom pack policy for env-profile',
:query => 'ciClassName:manifest.Environment AND _missing_:ciAttributes.profile'
:docUrl => '<document url link for the policy>'`
:mode => 'passive'
policy "compute-ostype",
:description => 'custom pack policy for compute-ostype',
:query => 'ciClassName:(catalog.*Compute manifest.*Compute bom.*Compute) AND NOT ciAttributes.ostype:("centos-6.5" OR "centos-6.6" OR "redhat-6.5" OR "redhat-6.6" OR "default-cloud")'
:docUrl => '<document url link for the policy>'`
:mode => 'active'
policy "env-automation",
:description => 'custom pack policy for env-automation',
:query => 'ciClassName:manifest.Environment AND ciAttributes.profile:(PROD EBF STAGING) AND NOT (ciAttributes.autorepair:true AND ciAttributes.autoreplace:true)'
:docUrl => '<document url link for the policy>'`
:mode => 'passive'
Brief description about each field in the policy definition is as follows