Feature request: ability to use non-"local" policy_group when exporting policies

[jayhendren]

When running integration tests via TestKitchen, it would be useful to test behavior dependent on the value of policy_group. However, chef export hardcodes the value of policy_group to local:

      # Policy groups provide namespaces for policies so that a Chef Server can
      # have multiple active iterations of a policy at once, but we don't need
      # this when serving a single exported policy via Chef Zero, so hardcode
      # it to a "well known" value:
      POLICY_GROUP = 'local'.freeze

This is a proposal for a feature that would allow setting the value of policy_group via a per-suite setting in .kitchen.yml. On the ChefDK side, this would require making POLICY_GROUP a configurable option to chef export.

[mattcl]

Any updates on this? This is sort of a barrier with poise-hoist and an air-gapped environment that requires a different policy_group other than local.

[jugatsu]

Any updates?

[AustinSmart]

Any updates on this?

[marcparadise]

While this would be a good feature, it is not currently on our roadmap. If you or any contributor is interested in opening a PR for this feature we'd be happy to provide feedback.