However currently the heat::policy class is not loaded when generating config files for heat-engine service, and the oslo.policy options are not rendered into the heat.conf file for heat-engine.
This prevents users from setting resource type policy rules by HeatApiPolicies.
Steps to reproduce
==================
* Create an environment file to define a resource type policy by HeatApiPolicies.
Description /bugs.launchpad .net/puppet- heat/+bug/ 1983340
===========
The heat-engine service requires access to policy rules so that it can enforce policy rules for resource types.
https:/
However currently the heat::policy class is not loaded when generating config files for heat-engine service, and the oslo.policy options are not rendered into the heat.conf file for heat-engine.
This prevents users from setting resource type policy rules by HeatApiPolicies.
Steps to reproduce
==================
* Create an environment file to define a resource type policy by HeatApiPolicies.
parameter_ defaults: cies: resource_ types:OS: :Nova:: Flavor' : ''
HeatApiPoli
'
* Deploy overcloud/ standalone with the environment file
* Create a stack with the flavor by a non-admin user
Expected result
===============
* Stack creation succeeds without error
Actual result
=============
* Stack creation fails because the user is not allowed to create a flavor resource
Environment
===========
* This issue was initially found in our downstream product based on stable/train
Logs & Configs
==============
N/A